Local workspace linking exposes broken package boundaries and webpack resolution assumptions across mashlib / solid-panes / solid-ui
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 70
- Forks
- 31
- Avg merge
- 4h 14m
- Merged PRs (30d)
- 5
Description
Linking solid-panes and solid-ui into mashlib
- webpack cannot resolve solid-ui and UI consistently from sibling workspace packages
- stale built artifacts and source/package export mismatch
- TypeScript config assumptions break when packages are linked but not fully installed/built
- current alias/declaration fixes are local workarounds, not the ideal package-boundary solution
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 reproducing the linked solid-panes and solid-ui workspace setup and inspecting webpack and TypeScript package-resolution assumptions. Compare the source/package exports and stale built artifacts, including the existing alias and declaration workarounds. Done means sibling packages resolve consistently when linked without requiring local fixes or fully prebuilt artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript, webpack
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100