-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Support the imports
field in the PnP API
#3843
Comments
Some packages like |
This comment was marked as spam.
This comment was marked as spam.
Fwiw: I recently encountered the same problem when installing latest version of Google zx@ 5.0.0 as they recently (4 days ago) upgraded their dependency on chalk to v5.0.0.
Using v4.3.0 of zx with yarn PnP works ok and is the workaround I'm using for now. |
Also upgrades Hugo to the same version. Due to a incompatibility of Yarn PnP with `imports` in `package.json`[1] declared by chalk version 5+, the resolution of chalk was set to the latest pre-5 version. Otherwise the postinstall script of hugo-extended would fail. [1] yarnpkg/berry#3843
Also upgrades Hugo to the same version. Due to a incompatibility of Yarn PnP with `imports` in `package.json`[1] declared by chalk version 5+, the resolution of chalk was set to the latest pre-5 version. Otherwise the postinstall script of hugo-extended would fail. [1] yarnpkg/berry#3843
Also upgrades Hugo to the same version. Due to a incompatibility of Yarn PnP with `imports` in `package.json`[1] declared by chalk version 5+, the resolution of chalk was set to the latest pre-5 version. Otherwise the postinstall script of hugo-extended would fail. [1] yarnpkg/berry#3843
Also upgrades Hugo to the same version. Due to a incompatibility of Yarn PnP with `imports` in `package.json`[1] declared by chalk version 5+, the resolution of chalk was set to the latest pre-5 version. Otherwise the postinstall script of hugo-extended would fail. [1] yarnpkg/berry#3843
Also upgrades Hugo to the same version. Due to a incompatibility of Yarn PnP with `imports` in `package.json`[1] declared by chalk version 5+, the resolution of chalk was set to the latest pre-5 version. Otherwise the postinstall script of hugo-extended would fail. [1] yarnpkg/berry#3843
Also upgrades Hugo to the same version. Due to a incompatibility of Yarn PnP with `imports` in `package.json`[1] declared by chalk version 5+, the resolution of chalk was set to the latest pre-5 version. Otherwise the postinstall script of hugo-extended would fail. [1] yarnpkg/berry#3843
Also upgrades Hugo to the same version. Due to a incompatibility of Yarn PnP with `imports` in `package.json`[1] declared by chalk version 5+, the resolution of chalk was set to the latest pre-5 version. Otherwise the postinstall script of hugo-extended would fail. [1] yarnpkg/berry#3843
Also upgrades Hugo to the same version. Due to a incompatibility of Yarn PnP with `imports` in `package.json`[1] declared by chalk version 5+, the resolution of chalk was set to the latest pre-5 version. Otherwise the postinstall script of hugo-extended would fail. [1] yarnpkg/berry#3843
I bump this. It looks like a serious problem. I encountered this in |
Someone have any workaround for this? |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as spam.
This comment was marked as spam.
I downgrade packages that use that. Fortunately there isn't a lot of them, mostly none. |
Is this work planned or in progress currently? I'd be happy to make an attempt to get this working. |
I am not affiliated with Yarn, but I, for one, would greatly appreciate that! We are trying to use AVA with Yarn PnP and ESM, and right now that simply isn’t possible to my knowledge. Unfortunately the first version of AVA with ESM support depends on the first version of Chalk that uses the |
There may be a general workaround involving packageExtensions:
chalk@5.0.1:
dependencies:
"#ansi-styles": npm:ansi-styles@6.1.0
"#supports-color": npm:supports-color@9.2.2 At least AVA loads.
AVA creates a |
Turns out the crash had nothing to do with AVA. It was simply caused by the lack of support for chaining loaders in Node.js. |
This comment was marked as spam.
This comment was marked as spam.
Please see this workaround in the meantime. |
Running into this in facebook/docusaurus#7684. Tried |
I don't know for sure, but all I can tell you is that I didn't use |
Describe the user story
Node supports an
imports
field inpackage.json
that the PnP API doesn't support yet.https://nodejs.org/dist/latest-v16.x/docs/api/packages.html#imports
Describe the solution you'd like
The PnP API should be updated to support it so packages that use it can work with PnP.
imports
lukeed/resolve.exports#14Describe the drawbacks of your solution
N/A
Describe alternatives you've considered
N/A
The text was updated successfully, but these errors were encountered: