Meteor-Community-Packages / Meteor-Community-Packages/meteor-typescript
Make work with "modern" swc BabelCompiler path in Meteor 3.3
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This doesn’t work as is.
One problem is that the sourceMap provided by our Typescript compilation step is not passed on to swc.
This should be possible by setting inputSourceMap in swcOptions via an override to inferExtraSWCOptions similar to how we do it for Babel in inferExtraBabelOptions.
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 locating inferExtraSWCOptions and compare it with inferExtraBabelOptions, then trace the modern BabelCompiler path and the TypeScript compilation sourceMap. Confirm that the source map reaches swc through inputSourceMap in swcOptions, and verify the Meteor 3.3 path works without regressing the existing Babel behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, typescript
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100