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
Currently some of our integrations use the CDN, which is great :) BUT we should allow an optional specifier to pin versions so people can have versions hard linked and can update when they want
What did you expect to happen?
We need to add a configuration parameter in the integration to optionally grab the latest CDN version. If that flag is false then the integration should only use the version of the CDN from its release version
Change Needed:
We need to inject the package.json version into the integrations (likely using Vite) and then use that value to fetch the appropriate CDN version. If the flag is set to grab latest then we grab latest instead.
The text was updated successfully, but these errors were encountered:
What happens?
Currently some of our integrations use the CDN, which is great :) BUT we should allow an optional specifier to pin versions so people can have versions hard linked and can update when they want
What did you expect to happen?
We need to add a configuration parameter in the integration to optionally grab the latest CDN version. If that flag is false then the integration should only use the version of the CDN from its release version
Change Needed:
We need to inject the package.json version into the integrations (likely using Vite) and then use that value to fetch the appropriate CDN version. If the flag is set to grab latest then we grab latest instead.
The text was updated successfully, but these errors were encountered: