John Reilly
John Reilly
I think aligning with tsc makes the most sense as it reduces the "distance" between tsc and working with webpack. Ideally I'd like any TypeScript loader to be a minimal...
Oh and additionally: for tooling reasons. I want to see the same output in VSCode / atom / brackets etc as I do from webpack. Otherwise I have to code...
Has anyone raised an issue with the TypeScript team itself to implement this behaviour in tsc? If they did implement then I would naturally be in favour of supporting this....
https://github.com/TypeStrong/ts-loader/issues/267
@colinskow are you sure that's correct? My understanding was that if you are going to specify `files` then you're required to specify *everything* in project scope. So `import` or `require`...
Ah - well that's news; thanks for sharing @colinskow, However, the problem is that it doesn't allow for multiple distinct entry points; i.e 2 different clashing project scopes driven by...
Somewhere somewhere I have a setup that demonstrates an issue with this. Alas I can't remember where... Perhaps my fears were unfounded - sounds like it
> Also when using esbuild as a webpack loader, we are not really leveraging the full speed benefits of esbuild This is true - but there's still a speed benefit...
I'm already using GA 4 with Docusaurus.... (Alongside old GA) Does anything actually need to be done here? https://github.com/johnnyreilly/blog.johnnyreilly.com/blob/4e824dc2172efca72c075f1dbc3a39a92fd22064/blog-website/docusaurus.config.js#L35
Yeah in fact that PR could use a tweak - I provided the wrong format I think. Will check