fix: support for node v16+ by migrating node-saas to saas and updating webpack from v4 -> v5 fixes #85 #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g webpack from v4 -> v5 fixes #85
…uired (mostly for current versions of babel)
activescott
added a commit
that referenced
this pull request
Sep 11, 2023
…g webpack from v4 to v5 (#94) support for node v16+ by migrating node-saas to saas and updating webpack from v4 -> v5 fixes #85 BREAKING CHANGE: removes support for node v10 and node v12. Node v16+ is now required (mostly for current versions of babel) Note: This commit is really a message to trigger a release based on conventional commits. The real changes are in 033714a
|
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this probably should be combined with other fixes to dependencies into a single release. Can publish to beta tag first.Locally npm audit showed no remaining vulnerabilities so I decided to push to main