4 ms·
The sane option would be to use a codemod to rewrite your code to not need bespoke tooling configurations. You are locking yourself into legacy tooling.
by lhnz 5y ago
The sane option would be to use a codemod to rewrite your code to not need bespoke tooling configurations. You are locking yourself into legacy tooling.
- dmitriid 5y ago> The sane option would be to use a codemod to rewrite your code to not need bespoke tooling configurations. 1. Absolute paths are not "bespoke tooling config", it's a tsconfig setting 2. Requiring some code to be served from a specific url is not "bespoke tooling config", it's a requirement for quite a few projects 3. Forcing someone to mindlessly and absolutely needlessly re-write thousands of import statements isn't really a solution 4. This will still not fix "failed to resolve "extends":"../../tsconfig.json"" and who knows what other errors
- ComputerGuru 5y ago> Forcing someone to mindlessly and absolutely needlessly re-write thousands of import statements isn't really a solution This is how progress is measured in the web world. The impact of your code/project/patch is measured by how many lines have to be rewritten to adopt it. The higher the number, the better your web wizardry rank is.