Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Parcel 2: Kotlin transformer
See original GitHub issueCreate the @parcel/transformer-kotlin package in packages/transforms/kotlin. This package is a Parcel 2 transform plugin for Kotlin. It should be based on the KotlinAsset from Parcel 1.
The @parcel/transformer-kotlin package is responsible for the following things:
- Compiling Kotlin to JS with
@jetbrains/kotlinc-js-api - Collecting all files referenced in the code so that Parcel watches them (not currently supported in Parcel 1)
- Generating source maps
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:5 (3 by maintainers)
Top Results From Across the Web
@parcel/transformer-toml | Yarn - Package Manager
Fast, reliable, and secure dependency management.
Read more >Parcel - Android Developers
Kotlin |Java ... A Parcel can contain both flattened data that will be unflattened on the other side of ... There are two...
Read more >Migration - Parcel
Parcel 2 now uses SWC instead, which improves transpilation performance significantly. However, the default transpiler has limited support for tsconfig.
Read more >parcel github
The parcel is bordered on two sides by US Forest Service and Washington DNR with ... Start using parcel-transformer-ejs in your project by...
Read more >Key Dofferences of Parcel vs Webpack - eduCBA
The transformers of the module are the tools that help the bundler to learn how it can read the files other than the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Do we really want this? Seems like there’s no way to know what assets to watch, the webpack plugin just uses globs and does not even use the official webpack watcher as far as I can tell. Seems pretty hacky for something that has a very small userbase.
Maybe not something we want to support as an official plugin
It’s not ideal, but works just fine (compiling multiple files into a single file is also done for Elm and Sass). This is more about cache invalidation than incremental compilation (so that Parcel known when that single JS file from Kotlin has to be regenerated)