Closed nenadvicentic closed 1 year ago
Thx very much for working on this! The parcel deps issue is bit strange. Probably parcel+yarn-pnp issue. I will test more and get back to you.
Unfortunately yarn pnp loose mode didn't help on the parcel issue :-(
@3cp After thinking a bit longer about this, I reworked the branch from scratch:
nodeLinker: node-modules
option in .yarnrc.yml
file. Now Yarn 2+ created node_modules
folder as well.strict-peer-dependencies=false
option for pnpm
in .npmrc
file. To avoid installation of packages breaking due to missing peer dependency. Thank you!
This pull request addresses issue #85.
When development machine has
yarn
version 2.x or higher installed (current version at the moment is 3.x), after developer chooses to installnpm
dependencies usingyarn
,yarn
works in Plug'n'Play mode. This means that nonode_modules
folder in created and allnpm
packages are stored in.yarn
folder unpacked, in originalzip
format.npm start
written in "Getting started" tip does not work.yarn start
is printed now, whenyarn
was picked as package manager.When using Visual Studio Code, for it's TypeScript language service to work Yarn's Editor SDKs extension is needed, to make TypeScript language service (local to the folder) aware of module resolution strategy.For Parcel not to throw errors, two dev-dependencies had to be added to project'spackage.json
: "@aurelia/runtime-html", "@aurelia/router" for direct-routing template and "@parcel/config-default".Now parcel starts/builds project without throwing errors.UPDATE: It turned out to be a problem to make Yarn's new PnP mode work seamlessly with different IDEs and bundlers. Switching Yarn 2+ to backward compatibility mode with
nodeLinker: node-modules
option, to force it to createnode_modules
folder seems like more stable and simpler option at the moment.