read-wasm abstraction
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3.7k
- Forks
- 370
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/mozilla/source-map/blob/11cecea2b64ead3f93cde37a5789dc7683685a7c/lib/wasm.js#L1
Is it possible to make read-wasm abstract in order to allow users to implement their own version ?
I encounter some difficulties to bundle source-map in server-side code generated through webpack.
https://github.com/mozilla/source-map/blob/11cecea2b64ead3f93cde37a5789dc7683685a7c/lib/read-wasm.js#L11-L12
has no sense in this context.
Thanks.
--edit--
Maybe you can allow https://github.com/mozilla/source-map/pull/339 for node.js ?
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 lib/wasm.js and lib/read-wasm.js, especially the referenced lines that perform the current read operation. Trace how read-wasm is used and consider the server-side webpack bundling constraint described in the issue. Done means consumers can provide their own implementation and the existing Node.js use case remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100