Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ui5-tooling-transpile] Provide custom path to tsconfig.json #1138

Open
philippkolbe opened this issue Dec 23, 2024 · 0 comments
Open

[ui5-tooling-transpile] Provide custom path to tsconfig.json #1138

philippkolbe opened this issue Dec 23, 2024 · 0 comments

Comments

@philippkolbe
Copy link

Problem
We are using the ui5-tooling-transpile-middleware to transpile our .ts files on build. We have several projects (i.e. one per app) and would like to share a tsconfig.json between all of those projects to avoid duplicating it.

We already only have one single shared .eslintrc.json between all apps. Not being able to share the tsconfig.json is especially annoying because the .eslintrc.json contains a path to a single tsconfig.json (overrides -> parserOptions -> project). This means that we need a single shared tsconfig.json anyways.

Sharing a tsconfig.json may seem a little counter-intuitive as it contains project specific configurations but we share code between different apps in a common library and therefore a shared tsconfig.json makes things easier.

Describe the solution you'd like
If we were able to provide a path to a tsconfig.json in the ui5.yaml specification we could share the tsconfig.json across apps.

Describe alternatives you've considered
We checked your library documentation but did not find any way to provide a path to a tsconfig.json. Copying all tsconfig.json files is possible but we would need to keep them in sync manually.

@philippkolbe philippkolbe changed the title Provide custom path to tsconfig.json [ui5-tooling-transpile] Provide custom path to tsconfig.json Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant