The component name/file name coupling in `webc:import="npm:"` feels a bit brittle
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 46
- Avg merge
- 10m
- Merged PRs (30d)
- 2
Description
https://fediverse.zachleat.com/@zachleat/109948320190919977
The current setup allows folks to reference any WebC component in a package pretty easily but it’d be nice to have a decoupled npm import that has a default file name too
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 reviewing the current webc:import="npm:" behavior and the linked discussion. Define how a decoupled npm import should select its default file name without coupling it to the component name; the work is done when that import path supports the intended default consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100