-
Notifications
You must be signed in to change notification settings - Fork 920
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
[pnpm] export detection not working for auto-detect packages (react-is, etc) #12
Comments
This sounds like thiir CLI doesn't support scoped packages, which is a bug on their end. Do you have any info on pnpx usage stats? |
No I don't. I find it much better than npm / yarn as it keeps a centralised module store instead of loading the full content of each module into each project, which also makes it much quicker to do installs etc., but most other developers I know have never heard of it. Feel free to close this issue if the original documentation works with normal npm client. |
Yea, this seems more like an issue with pnpx not matching npx correctly. Will close this issue for now, but if enough people continue to run into it we can reopen and see how the README can be clarified to point out the pnpx mismatch. |
Thanks for trying the tool out! |
@fineline you ever figure this out? |
Now that the library name doesn't have an "@", |
Just learned about snowpack today while trying to compile some es6. I tried running this demo: https://github.com/ryanlanciaux/snowpack-demo. Works with yarn. But trying with full output:
|
Thanks for the extra info/output. Okay, so we actually explicitly allow "react-is" as a dependency to ahead-of-time analyze imports. You can see it here. That means that one of two things is happening:
This will need some more debugging. I'll re-open this issue and hopefully someone can help debug (would love your help, if you're interested! Otherwise, I'll try to get to it when I have a spare moment). |
@FredKSchott I am flattered that you would ask for my help, but sadly, I have no idea what is going on here. If you wanted to give me some direction, I would take a stab at it. This was only half of what I wanted to do. I was actually trying to use this as a bundler for a reasonml app. Do you know if that is possible, maybe in configuration? Glad I could help. |
no problem! This may be a tricky one, feel free to poke around but no pressure if you don't feel comfortable. Unfortunately I don't have any intimate experience with ReasonML, but if it can compile to JS and load JS dependencies, then that's all it should need to work with Snowpack. |
update: assume that this is still happening, still looking for some help from someone who is using pnpm! |
To make it work, you just have to add The “problem”—a feature really—is More on the subject: Btw, |
If anyone has an example of the error you see today, please share! This issue is very old, and I have a feeling it is less blocking of an issue that it once was. If it is still happening, we can add some handling to Please share the error output if you run into it! |
Update from maintainers: See discussion below for updated issue: #12 (comment)
I use
pnpm
as an alternative npm client (because it uses a central module repo and symlinks, which saves tons of disk space). When following the guide in README, I replaced this line:with
which gave error:
So looking further down at the optional npm prepare script step, I saw that referenced "pika-web" and tried that instead:
Which seems to have worked much better. Not sure if the original version works properly with npx as I don't use it, but this version definitely seems better on
pnpx
.The text was updated successfully, but these errors were encountered: