Create a process to upload versions of commerce.js to CDN on release
See original GitHub issueThe build process of commerce.js
creates some bundles that can be used inside traditional <script>
tags if you don’t want to mess around with NPM. We should figure out a process (probably during npm publish
) that will upload these scripts to a CDN.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Getting started | Commerce.js docs
This documentation will walk you through how to: Set up a Chec account. Install Commerce.js into your project. Create a Commerce instance to...
Read more >Features - Commerce.js
Create infinitely nestable categories for product groups and collections. Add assets and descriptions to categories. Adding categories. Variants.
Read more >Building faster headless eCommerce applications
When you upload images to Chec/Commerce.js, we serve them back to you in the format you uploaded them in via our content delivery...
Read more >Release notes - Commerce.js
Keep up to date with the latest release notes for Commerce.js and the Chec Platform.
Read more >Listing products with React.js | Commerce.js docs
This guide will show you how to create a simple list of products from Chec using Commerce.js and React.js. Overview. In this example...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The CDN has the 2.0.0 release that @robbieaverill tagged yesterday so I assume I fixed this and forgot to update the issue!
I was thinking that we’d upload per major.