-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] use ttypescript under the hood to enable applying TS transforms #719
Comments
update: it's actually meant to be passed as a transform to |
First of all, thank you for opening a PR. Can you elaborate a little bit on why we want to allow typescript transformers? Why not go for a babel plugin? I'm worried that if we swap typescript with a third party compiler, we will open up to more bugs that are not related to microbundle itself. |
I actually tried using a relevant Babel plugin but it didn’t seem to work, possibly because of the order of tools? Not quite sure.
For example, I wanted to run the styled-components Babel plugin over some code but adding it to babelrc had no effect.
|
I would also be in favor of including ttypescript so that I can use https://www.npmjs.com/package/ts-transformer-properties-rename to rename TS properties. |
from https://github.com/cevek/ttypescript#what-it-is:
ttypescript uses typescript under the hood. I don't BELEIVE anything should break. However, smoke tests should be written if no one else is certain. |
Yeah it basically just allows the rollup plugin to also look at tsconfig.json :) |
FWIW @berndartmueller Microbundle already provides that exact feature: // package.json
{
"mangle": {
"properties": "^_"
}
} |
@developit I think I'd say |
Maybe instead of hardcoding it to |
https://www.npmjs.com/package/ttypescript
The main benefit of going with this solution is being able to specify transformer plugins in
tsconfig.json
so it's an easy configurationThe text was updated successfully, but these errors were encountered: