Which config could be moved to the parent dir?

[danieldietrich]

• eslint searches the configuration in the parent dir
• ./tsconfig.json could extend ../tsconfig.json
• etc.

This would only make sense if all projects have roughly the same shape, e.g. being node projects.

[spoenemann]

Typescript allows to have a base config that can be extended. That is super useful, so all packages can share settings about compiler checks etc.

Example: https://github.com/eclipse/sprotty/blob/master/tsconfig.json

[danieldietrich]

Thx, yes, we already use that in Langium for excluding unit tests from the build (that are considered in the development build). I will move that base config to the root.

[danieldietrich]

I've experimented a bit and there seem to emerge more problems that moving config is being helpful.

For example, plugins like typescript-esling/eslint-plugin (for eslint) or jest (for tsconfig) need to be present in the root node_modules folder. Also includes/excludes aren't recognized anymore and need to be overridden in the project-specific configs.

For now I see no benefit in moving (some) configs to the root, so I will close this issue.