Skip to content

Extend Arrays In Tsconfig #56223

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

Closed
5 tasks done
enchorb opened this issue Oct 26, 2023 · 2 comments
Closed
5 tasks done

Extend Arrays In Tsconfig #56223

enchorb opened this issue Oct 26, 2023 · 2 comments
Labels
Duplicate An existing issue was already created

Comments

@enchorb
Copy link

enchorb commented Oct 26, 2023

🔍 Search Terms

I am unable to use both tsconfig.base paths (nx monorepo libs) and tsconfig.local paths (relative path cleanup).

Good solutions are mentioned here #20110

Opening this with another issue because that one is from 2017 and seems to largely have fallen off the radar

✅ Viability Checklist

  • This wouldn't be a breaking change in existing TypeScript/JavaScript code
  • This wouldn't change the runtime behavior of existing JavaScript code
  • This could be implemented without emitting different JS based on the types of the expressions
  • This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
  • This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

An <inherit> peoprty for tsconfig files. See here for more: #20110

📃 Motivating Example

See here for more: #20110

💻 Use Cases

  1. What do you want to use this for?
  2. What shortcomings exist with current approaches?
  3. What workarounds are you using in the meantime?
@xiBread
Copy link

xiBread commented Oct 26, 2023

There's no point in making another issue if there's already one open.

@RyanCavanaugh RyanCavanaugh added the Duplicate An existing issue was already created label Oct 26, 2023
@RyanCavanaugh
Copy link
Member

Making duplicates on purpose is a misuse of the issue tracker and is not appropriate behavior. Further violations will result in a block.

@RyanCavanaugh RyanCavanaugh closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

3 participants