Skip to content

Conversation

vladima
Copy link
Contributor

@vladima vladima commented May 5, 2015

...nd 'separateCompilation' flags are specified (used in 'transpile' related scenarios)

This PR forces emit for in-browser transpile scenarios when .js es6 file is converted to downlevel

…' and 'separateCompilation' flags are specified (used in 'transpile' related scenarios)
if ((isExternalModule(sourceFile) || !compilerOptions.out)) {
// 1. in-browser single file compilation scenario
// 2. non .js file
return (compilerOptions.separateCompilation && compilerOptions.allowNonTsExtensions) ||
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not just compilerOptions.allowNonTsExtensions?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wanted to be sure that this is enabled only for in-memory transpile scenario where we set these two properties

@vladima
Copy link
Contributor Author

vladima commented May 5, 2015

approved offline by @mhegazy

vladima added a commit that referenced this pull request May 5, 2015
emit input non .ts files as separate files when 'allowNonTsExtensions' a...
@vladima vladima merged commit 3c9a3c5 into master May 5, 2015
@vladima vladima deleted the outputJsFiles branch May 5, 2015 01:02
@microsoft microsoft locked and limited conversation to collaborators Jun 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants