ENOTDIR in Nuxt bridge with pinia v0.4.0+
Open
Nobody has claimed this yet.
bug
workaround available
- Dominant language
- TypeScript
- Stars
- 285
- Forks
- 33
- Avg merge
- 22h 38m
- Merged PRs (30d)
- 3
Description
Trying to upgrade to v0.4.0 with Nuxt bridge and trying to build the application gives me:
ERROR Rollup error: ENOTDIR: not a directory, stat '/.../node_modules/.pnpm/pinia@2.0.20_typescript@4.7.4+vue@2.7.9/node_modules/pinia/dist/pinia.mjs/dist/pinia'
FATAL ENOTDIR: not a directory, stat '/.../node_modules/.pnpm/pinia@2.0.20_typescript@4.7.4+vue@2.7.9/node_modules/pinia/dist/pinia.mjs/dist/pinia'
Here you go: https://codesandbox.io/s/nuxt-pinia-evblty
Run a yarn build to reproduce the error.
Originally posted by @dargmuesli in https://github.com/vuejs/pinia/discussions/1582.
Contributor guide
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
Open the linked CodeSandbox and run yarn build to reproduce the Rollup ENOTDIR error involving Pinia under the Nuxt bridge. Trace the build's module-resolution path around the reported pinia.mjs/dist/pinia location. Done means the application builds without this ENOTDIR failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- build-system, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100