How do we use a Release? #293
-
|
How do we use a release from https://github.com/fermyon/spin-js-sdk/releases (e.g. https://github.com/fermyon/spin-js-sdk/releases/tag/v2.2.0)? Aren't these releases supposed to be delivered as a spin plugin? As such, there should be a, e.g., 2.2.0, version in https://github.com/fermyon/spin-plugins/tree/main/manifests/js2wasm? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hey, @rgl, great to see you again! A few months ago we introduced the v2 of the JS SDK which no longer requires a plugin -- more details in this post https://www.fermyon.com/blog/introducing-the-new-js-sdk and the docs for the new SDK https://developer.fermyon.com/spin/v3/javascript-components#building-and-running-the-template. TL; DR is that v2 is a breaking change in case you have existing apps built with v1 of the JS SDK. If you're starting a new app, then using the template brings in the desired version of the SDK. Let me know if this makes sense. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! I've missed those posts, which I've now read and was able to update my example. :-) |
Beta Was this translation helpful? Give feedback.
Hey, @rgl, great to see you again!
A few months ago we introduced the v2 of the JS SDK which no longer requires a plugin -- more details in this post https://www.fermyon.com/blog/introducing-the-new-js-sdk and the docs for the new SDK https://developer.fermyon.com/spin/v3/javascript-components#building-and-running-the-template.
TL; DR is that v2 is a breaking change in case you have existing apps built with v1 of the JS SDK.
If you're starting a new app, then using the template brings in the desired version of the SDK.
Updates and new releases are consumed by bumping the version number in package.json.
Let me know if this makes sense.