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
Incorrect order of extend()ing compilerOptions #27
Comments
@terasaka2k This is correct. The Edit: Accidentally hit enter. |
Consider this use case: I'm using webpack to chain the typescript-loader and the babel-loader together to take advantage of babel's hook runtime for things like HMR. I want my tsconfig.json to target ES6 and let the babel-loader transpile from ES6 to ES5 for browsers. However, in my server code, I want to go straight from TS to ES5. I would like to be able to do this:
And then what I would expect to happen in ts-node would be something like:
|
@darthtrevino I'm not sure who you're responding to, but that's how it works already and the reason I closed the issue. However, there's no |
It sounds like you're actually after a different feature? The ability to pass in compiler options that override |
Correct |
Sweet! Thanks @blakeembrey ! |
In ts-node.ts around line 80,
should be
for
{ target: 'es5', module: 'commonjs' }
to take precedence over user's options, which potentially may be intended for latest browsers environments.The text was updated successfully, but these errors were encountered: