@parcel/fs tried to access @parcel/core (a peer dependency) but it isn't provided by its ancestors error when following tutorial
#9114
Comments
|
can you give a reproduction link? https://codesandbox.io/ will be great |
|
I'm having the same issue. triggers the problem. |
|
I made a codesanbox here: https://codesandbox.io/p/sandbox/zealous-https-z83pz3 |
|
please, add @parcel/core to your dev dependencies) And everything will work fine: link to reproduction - https://codesandbox.io/p/sandbox/gallant-haze-t9qjqh?file=%2Fsrc%2Findex.html%3A10%2C13 Also i would recommend to add index.html to src/ folder 🙂 |
That's was for the demo.
The getting started doesn't mention this. Also, this workarounds doesn't works on bigger projects: A "stable" workaround is to put yarn pnp in "loose" mode. |
I'm a simple dev like you, i don't have permision to edit docs 🙂
I see that parcel in your dependencies is not similar with @parcel/ packages, maybe this is an issue) |
Ah it's just the leftover of me trying to see if it's a recent parcel change. The behavior are the same on the lastest version. |
|
Thanks for all the feedback. 🙏 This does seem to be a real issue with following the docs with Yarn then. 🤔 (I ended up skipping Parcel for my (very simple, rudimentary) project. I detest Node.js anyway. 😉 🙈) |
|
In conclusion to this, i think Parcel need to update docs to install @parcel/core in dev dependencies too) |
As I said, it doesn't solve the issue on larger projects. |
|
FYI, Yarn's own E2Es are also broken because of this: https://github.com/yarnpkg/berry/actions/runs/5794322982/job/15703692932 |
|
I agree that the proper solution is to fix the dependencies in the corresponding packages. What you can do as a workaround is to use yarn's package extension mechanism, e.g. by putting something like the following into your packageExtensions:
"@parcel/node-resolver-core@*":
dependencies:
"@parcel/core": 2.9.3For projects with multiple workspaces, this applies the extensions to all of them. You might need to add ➤ YN0002: │ @parcel/types@npm:2.9.3 doesn't provide @parcel/core (pf46c3), requested by @parcel/fs
➤ YN0002: │ @parcel/types@npm:2.9.3 doesn't provide @parcel/core (p16f90), requested by @parcel/workers
➤ YN0002: │ @parcel/types@npm:2.9.3 doesn't provide @parcel/core (p385c8), requested by @parcel/cache
➤ YN0002: │ @parcel/types@npm:2.9.3 doesn't provide @parcel/core (p76fb9), requested by @parcel/package-manager |
|
Any progress on this? I'm stuck. No luck. |
|
@olivier-spinelli Sorry to hear that. What's the error you're seeing, the same as in my original issue description? |
|
Sorry for the delayed answer. |
|
[TEMP SOLUTION] I had to create .yarnrc.yml file in the root of my project and add the following in it: packageExtensions:
"@parcel/node-resolver-core@*":
dependencies:
"@parcel/core": 2.9.3
"@parcel/types@*":
dependencies:
"@parcel/core": 2.9.3
"@parcel/fs@*":
dependencies:
"@parcel/core": 2.9.3Save file and run My package.js devDependencies looks like this now (ignore the packager-raw-url, transformer-webmanifest): Everything works now. Hope it helps someone. |
|
In my case I don't have this issue after switching to |
|
Just preventing the Bot from closing this issue. |
## What's the problem this PR addresses? It seems like the issue (parcel-bundler/parcel#9114) is stuck on Parcel's side with no interest of it being fixed. ## How did you fix it? While this is not ideal, that leaves us with two choices: add a workaround and continue testing Parcel, or remove E2E tests for Parcel altogether. I chose the former. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed.
|
I am having this error after adding parcel and Extending dependencies for |
|
So about 2 weeks ago, I was able to get this work in an npm workspace without issue. Today, I am doing the same thing with yarn and I'm getting this error: Here are the commands I ran: I'll try to get you a reproduction but you can just follow the steps here, most of which are based off of the documentation of this project and some tips from this issue. I was really loving parcel until running into this... |
|
|
|
@hrynevychroman Thanks, your solution worked for me. |
🐛 bug report
Following the general tutorial at https://parceljs.org/getting-started/webapp/ gives me the error below when trying to run
yarn parcel src/index.html.The
yarn addstep worked fine and addedparcelproperly to the mypackage.json.🎛 Configuration (.babelrc, package.json, cli command)
package.json{ "name": "example.com", "packageManager": "[email protected]", "devDependencies": { "parcel": "^2.9.3" } }I don't have any
.babelrcAFAICT.🤔 Expected Behavior
The app should be built and the devserver should be started.
😯 Current Behavior
💻 Code Sample
N/A at the moment, but can be provided if needed.
🌍 Your Environment
asdfThe text was updated successfully, but these errors were encountered: