solidjs / solidjs/solid-playground
Compiler not published as ESM?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 244
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
Just noticed this as I was poking around
How is this meant to be used in a browser, since browsers don't support commonjs?
might be related to https://github.com/solidjs/solid-playground/issues/174
thanks!!
tho, maybe I don't know what's going on here -- esm.sh thinks there are exports
Searching through https://esm.sh/v135/solid-repl@0.26.0/es2022/dist/compiler.js
it's kind of hard to see what is actually exported, since so much content is in strings 😅
(turns out esm.sh is a better source viewer than npm haha)
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 by inspecting the published solid-repl@0.26.0 dist/compiler.js package and the related solid-playground issue #174, then reproduce the browser import behavior described here. Determine whether the compiler package exposes a usable ESM entry; done means the intended browser usage is clear and the published package works accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100