Print filepaths using Svelte or SvelteKit-specific code in @sveltejs/package
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the problem
svelte-package warns you when you include a Svelte-specific or SvelteKit-specific import in your package but do not include it in dependencies or peerDependencies. If not including dependencies or peerDependencies was intentional, finding the file that uses the wrong import takes a minute.
Describe the proposed solution
It would be helpful if svelte-package printed the file in the terminal. Preferably with a link you can Ctrl+Click in VS Code to jump to the file immediately.
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response
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 at the svelte-package warning that reports Svelte-specific or SvelteKit-specific imports. Trace how the warning is printed in the terminal and determine how the importing filepath can be included with a VS Code-compatible link. Done means the warning identifies the file containing the import.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100