Skip to content
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.

fix(deps): Always use latest version of html-sketchapp #32

Merged
merged 1 commit into from
Apr 4, 2018

Conversation

markdalgleish
Copy link
Member

In order to use html-sketchapp in a browser context, we need to compile it into a browser-compatible script file. Currently, we do this by running the script through webpack before publishing to npm.

The downside of this approach is that consumers are locked to the version of html-sketchapp that we bundle at publish time. If a new version of html-sketchapp is released, it won't be available to consumers of this tool until we trigger another release.

To fix this, we now run the script through Rollup at runtime, which means that it's always using the version of html-sketchapp that's currently installed in node_modules.

Since it's now possible that an html-sketchapp update could cause the compilation step to fail, I'm also adding a Renovate config so that we keep up with downstream updates and ensure that the build continues to pass.

@markdalgleish markdalgleish changed the title feat(html-sketchapp): Always use latest version of html-sketchapp feat: Always use latest version of html-sketchapp Apr 4, 2018
@markdalgleish markdalgleish changed the title feat: Always use latest version of html-sketchapp feat(deps): Always use latest version of html-sketchapp Apr 4, 2018
@markdalgleish markdalgleish changed the title feat(deps): Always use latest version of html-sketchapp fix(deps): Always use latest version of html-sketchapp Apr 4, 2018
@markdalgleish markdalgleish merged commit 6d059c0 into master Apr 4, 2018
@markdalgleish markdalgleish deleted the always-use-latest-html-sketchapp branch April 4, 2018 22:59
@seek-oss-ci
Copy link

🎉 This PR is included in version 0.4.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants