Set preferUnplugged to true #4
Merged
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
|
LGTM |
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.
When using Yarn, the package is installed through Yarn PnP. This causes it to be stored in a zip, using either virtual folders or a zip filesystem. Because this is a compiled
wasmplugin, and swc does not have support for loading plugins from the zipfs, the plugin fails to load when used with an obscured error.The local workaround was to use
yarn unplugwhich saves adependenciesMetafield to the project package.json, but that is obviously not ideal, considering the plugin shouldn't work in any cases in which it uses PnP and it should be unplugged by default.See https://yarnpkg.com/configuration/manifest#preferUnplugged for the docs on this package.json property.