vitest-dev / vitest-dev/vitest
Failed to resolve entry for package "@sveltejs/package".
Open
Nobody has claimed this yet.
p4-important
- Dominant language
- TypeScript
- Stars
- 17.1k
- Forks
- 2k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 94
Description
Describe the bug
See the video!
The error happens when update to latest version (0.34.1).
https://github.com/vitest-dev/vitest/assets/130963/4d1bd2fa-bcde-4adf-ae5b-cf6440d73d16
Reproduction
I don't know if it's just a sveltekit problem.
To get the error, update vitest to latest version (0.34.1).
Example:
| status | version | url |
|---|---|---|
| Error | 0.34.1 | https://stackblitz.com/edit/sveltejs-kit-template-default-5ewdfa?file=package.json |
| Ok | 0.33.0 | https://stackblitz.com/edit/sveltejs-kit-template-default-l1xw6t?file=package.json |
Open the link and run:
npm test
System Info
System:
OS: macOS 13.3.1
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Memory: 628.38 MB / 32.00 GB
Shell: 3.5.1 - /usr/local/bin/fish
Binaries:
Node: 18.16.0 - /usr/local/bin/node
Yarn: 1.22.19 - ~/.npm-global/bin/yarn
npm: 9.7.1 - ~/.npm-global/bin/npm
pnpm: 8.6.0 - ~/.npm-global/bin/pnpm
Browsers:
Chrome: 115.0.5790.170
Chrome Canary: 117.0.5928.0
Safari: 16.4
### Used Package Manager
pnpm
### Validations
- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
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 StackBlitz reproduction and inspect package.json, then run npm test with Vitest 0.34.1 and compare it with 0.33.0. Done means the SvelteKit reproduction no longer fails to resolve @sveltejs/package after updating Vitest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- devtools, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100