pnpm install
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.1k
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
Is there still any known issue with `pnpm` like it was [earlier mentioned](https://github.com/lukeed/pwa/issues/24#issuecomment-418556564)?
```sh
> pnpm watch
[PWA] Applying preset: @pwa/preset-svelte
[PWA] Starting development server on http://localhost:8080
[PWA] Failed to compile! Found 1 error:
multi ./index.js ../node_modules/.pnpm/webpack-dev-server@3.11.2/node_modules/webpack-dev-server/client/index.js ../node_modules/.pnpm/webpack@4.46.0/node_modules/webpack/hot/dev-server.js
Module not found: Can't resolve 'babel-loader' in '$HOME/path-to-root/src'
```
Analogous error message running directly `pwa init` (still globally installed with `pnpm add -g @pwa/cli`)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with `pnpm watch` and `pwa init`, using the reported `@pwa/preset-svelte` setup and the missing `babel-loader` message as the starting point. Determine whether the commands resolve dependencies correctly under pnpm; done means both entry points compile or initialize without the reported module-resolution error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- build-system, cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100