You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JS files used by the demo import augurs dependencies from the dist directory, but that directory just contains a static build of augurs rather than one built during CI. IIRC I did this to simplify the initial deployment of the demo to Cloudflare Pages, but it's not great because it's not being updated as new features/bugfixes are added.
However, I can't see Cloudflare Pages' build stage being able to build the augurs JS library from source since it requires a Rust toolchain and a bunch of other stuff (wasm-pack etc). What's the best way to make sure the demo is using the latest version?
From what I can see the options are:
use a JS framework and get Cloudflare Pages to build it using the latest published version - probably fine? but annoying to have to add a build stage
use some sort of hook & CI check to ensure the augurs build in demo/dist is up-to-date - more error prone and frustrating when I forget to update it...
The text was updated successfully, but these errors were encountered:
The JS files used by the demo import augurs dependencies from the
dist
directory, but that directory just contains a static build of augurs rather than one built during CI. IIRC I did this to simplify the initial deployment of the demo to Cloudflare Pages, but it's not great because it's not being updated as new features/bugfixes are added.However, I can't see Cloudflare Pages' build stage being able to build the augurs JS library from source since it requires a Rust toolchain and a bunch of other stuff (wasm-pack etc). What's the best way to make sure the demo is using the latest version?
From what I can see the options are:
demo/dist
is up-to-date - more error prone and frustrating when I forget to update it...The text was updated successfully, but these errors were encountered: