Lock swc & Default projectName in builders#229
Merged
Mortaro merged 3 commits intonullstack:unstable-nextfrom May 10, 2022
Merged
Lock swc & Default projectName in builders#229Mortaro merged 3 commits intonullstack:unstable-nextfrom
Mortaro merged 3 commits intonullstack:unstable-nextfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Looks like the release of @swc/core v1.2.180 was skipped because of tests not passing.
Then happened the release of v1.2.181, which caused compilations to break at linux environments (e.g. Vercel hosts) with errors envolving the inability to import the build results from .production/server.js.
releases comparison v1.2.179...v1.2.181
commit with error at v1.2.180
Solution: Locking swc at a well-tested version and manually update&test in the future.