typescript-compile | Automatically compile TypeScript to JavaScript on the fly | Runtime Evironment library

If writing this in a create-react-app project then VS-Code complains about the last line export { MyInterface}

Hi I'm using the clearscript V8 engine and want to enable TypeScript.

Following this post I'm able to load the https://rawgit.com/Microsoft/TypeScript/master/lib/typescriptServices.js javascript code into V8 and use that to transpile typescript code, but is seems to use an old version ES3 as a default target for the transpiled js.

How can I set the transpilation target to ES2021? All guidance is about tsconfig used with tsc.exe but I can't seem to figure out how to do this when using typescript.js straight in V8.

Like lodash, the library @yamato-daiwa/es-extensions suggests the common functions for both BrowserJS and NodeJS, but unlike lodash it has single main file index.js with re-exports.

This library:

1. Must work in browser environment with Webpack (reached ✔️)
2. Must make available the Webpack's tree shaking (by other words, the cutting off of the unused functionality on production building) for BrowserJS where each kilobyte on count (reached ✔️).
3. Must work in NodeJS environment.
4. Must work with ts-node

The conflicting point is the modules type. To make the Webpack's tree shaking available, the ES modules are required, but currently NodeJS supports CommonJS modules only, and in ts-node the ES modules support is limited (especially in the library exporting case).

What we have is:

Because the tree shaking is critical for BroswerJS, it's already been decided to distribute the library by ES2020 modules. But this way, the support for NodeJS and ts-node will be lost.

Even if to build the NodeJS application with Webpack where it's not recommended to bundle the NodeJS libraries (webpack node modules externals is being used to exclude them), application will crush if don't add the @yamato-daiwa/es-extensions with it's ES modules to excluding of webpack node modules externals.

In this repro, npm run "Webpack:ProductionBuild" will build the files BrowserJS.js and NodeJS.js for appropriate environment. Because the source code using isUndefined function of "@yamato-daiwa/es-extensions" library only, in BrowserJS.js must not be any other functionality (Webpack's tree shaking):

Numerous blog posts and the using-typescript example on Gatsby JS's website show using a tsconfig.json file when using the automatically included gatsby-plugin-typescript TypeScript support for Gatsby. I don't think the tsconfig.json file is being used for config, and want to ask if I'm correct.

Gatsby uses @babel/plugin-transform-typescript to compile TS to JS, and that Babel plugin has detailed docs on imitating the options of the tsc TypeScript compiler with it. The docs say this:

Changes to your tsconfig.json are not reflected in babel. The build process will always behave as though isolatedModules is turned on, there are Babel-native alternative ways to set a lot of the tsconfig.json options however.

Am I missing some reason for why all of the TypeScript setups for Gatsby show a tsconfig.json file and config when that file appears never to be used by Gatsby?

I've already seen this other question, but although the name is similar, the question is really a different one, because they're trying to get the type of a property, which happens to be the same as the generic type argument, but I'm trying to get the actual resolved type argument, because I want to get the type T of Array, and there's no property of type T inside the array type.

So I have a function like this:

I have a .d.ts file, and would like to compile it down to a .js file. Is this possible using the tsc command?

I know that the tsc command can take any .ts file and then compile it down .js file (I have tested this). However, I couldn't get it to take a .d.ts file as an input since it did not output any .js file for me.

I have tried to play around with tsconfig.json and this how my file looks like at the moment:

Assume I get from the api an object which looks like this:

I appreciate that this is likely a naive question, however I am trying to find my way in the dark and the documentation from Microsoft really isn't as intuitive as I need it to be, since I've never worked with either Visual Studio Code or TypeScript before.

• I have installed Visual Studio Code (version 1.51.1)
• Visual Studio Code > Help > About references Node.js 12.14.1 - I'm not sure if it's telling me that it has included that in its own install or if it needs that to work properly
• I have downloaded TypeScript for Visual Studio 2015 (from https://www.microsoft.com/en-us/download/details.aspx?id=48593) and successfully installed it by following the excellent and clear instructions from @Neurotransmitter

I have written and saved a basic .ts file:

Supposing we have a generic class or an interface: