tsconfig.json suggestions about fuse-box

[devmondo]

the way i see it is really simple, just provide option to take the path relative to project dir, and feed it to TS and that is all. Fuse is now and should always be transparent about plugins, in essence it should only receive content wither it is compiled or not and do the bundling.

[nchanged]

Thank you very much for the ideas.
Good thinking. I was expecting someone to raise that topic sooner or later =)

• tsconfig.json will be configurable (it was on my list)
• Can be done (any suggestions how?)
• I guess it's a bug. .tsx should trigger typescript mode.

When you are in typescript mode and do an import that looks like import foo from "./foo" FuseBox has to know that you are referring to a .ts extension not .js

Let me know what you think

Cheers

[kdmadej]

Regarding the strictness: I think this suggestion is a plausible approach (read the contents, minify, feed into JSON.parse).
Another way to do this would be to mimic the behaviour of ts itself, as depicted in the pr that introduced comments to tsconfig.

Although the best solution in my opinion would be for ts to expose a parseConfigFile method to help developers maintain a consistent way of parsing the config file across projects that depend on it. I guess I'll post a suggestion on their issue tracker.

EDIT: apparently the aforementioned parseConfigFileTextToJson() is already exposed. Example usage:

const fs = require('fs');
const ts = require('typescript');

const configPath = './tsconfig.json';
const tsconfig = fs.readFileSync(configPath).toString();
const parsedConfig = ts.parseConfigFileTextToJson(configPath, tsconfig); // the first argument seems to be used only for diagnostics
// parsedConfig.config contains the configuration object that can be passed to fuse-box

[devmondo]

this is now supported, please reopen if otherwise :)