codesandbox / codesandbox/codesandbox-client
Sandbox can't recognize Subpath imports, compile fail when import npm package which use this syntax
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
How has this issue affected you? What are you trying to accomplish?
To Reproduce
-
sandbox can't recognize Subpath imports (https://nodejs.org/api/packages.html#subpath-imports)
-
please see this demo: https://codesandbox.io/p/sandbox/vfile-pure-3xfl7w?file=%2Fsrc%2Findex.mjs%3A16%2C1
The new version vfile use this syntax, codesandbox can't preview it.
Link to sandbox: link (optional)
https://codesandbox.io/p/sandbox/vfile-pure-3xfl7w?file=%2Fsrc%2Findex.mjs%3A16%2C1
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | |
| Browser | |
| Operating System |
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
Start with the linked CodeSandbox reproduction and src/index.mjs at the reported line, then compare its package resolution behavior with Node.js subpath imports. Done means the vfile-pure sandbox preview compiles and recognizes the subpath import syntax.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100