You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I thought it might be useful. I often have to use large tools like esbuild to simply transform TypeScript to JavaScript without actually doing anything complicated. I would gladly give them up in favor of this library. On the one hand, I think it is an interesting development, but I would not be inclined to extend the current API. I think it is complete, and that is great. If I were to solve this problem, I would create a separate ts-blank package that would include a very simple set of CLI-specific features, as well as a loader for Node.js. Yes, the current solution already contains a loader, but I would conceptually separate it. For now, these are just thoughts; I wanted to share them and learn yours.
Usage: ts-blank [options]
Options:
--tsconfig Path to the tsconfig.json
We can use the typescript --showConfig and access files, compilerOptions.rootDir, compilerOptions.outDir fields. The compilerOptions.allowImportingTsExtensions could be usefull too.
The text was updated successfully, but these errors were encountered:
Yeah, I completely agree. One goal of ts-blank-space is to remain focused on having one responsibility allowing other packages to wrap it and add extra functionality such as a CLI or bundler integrations.
What's the status on this @vanyauhalin? I was going to switch from tsc because it started giving me headaches on a legacy JS project where we are introducing TS and I think this would be a better alternative but introducing webpack to use ts-blank-space is not a good solution. A CLI like tsc would make this really killer...
@davidrhoderick Hi, David. I have a prototype of this CLI. It works, but it is not published yet. I have switched to other projects that do not use JavaScript at all, so the work has paused a bit. The fact that you wrote to me indicates that I am not the only one who needs this kind of CLI. I am glad you did. I will not promise anything, but I will try to get back to work as soon as possible.
I thought it might be useful. I often have to use large tools like esbuild to simply transform TypeScript to JavaScript without actually doing anything complicated. I would gladly give them up in favor of this library. On the one hand, I think it is an interesting development, but I would not be inclined to extend the current API. I think it is complete, and that is great. If I were to solve this problem, I would create a separate
ts-blank
package that would include a very simple set of CLI-specific features, as well as a loader for Node.js. Yes, the current solution already contains a loader, but I would conceptually separate it. For now, these are just thoughts; I wanted to share them and learn yours.We can use the
typescript --showConfig
and accessfiles
,compilerOptions.rootDir
,compilerOptions.outDir
fields. ThecompilerOptions.allowImportingTsExtensions
could be usefull too.The text was updated successfully, but these errors were encountered: