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

ts-node field declared in extended tsconfig.json #1328

Closed
jjangga0214 opened this issue May 22, 2021 · 2 comments · Fixed by #1356
Closed

ts-node field declared in extended tsconfig.json #1328

jjangga0214 opened this issue May 22, 2021 · 2 comments · Fixed by #1356
Milestone

Comments

@jjangga0214
Copy link

jjangga0214 commented May 22, 2021

Desired Behavior

When "ts-node" field is configured in extended tsconfig, it should also work.

For example, let's say there are tsconfig.root.json and tsconfig.json.
"ts-node" is declared in tsconfig.root.json and tsconfig.json extends it.

tsconfig.root.json

{
  "compilerOptions": {
    // ... some configuration
  },
  "ts-node": {
    "transpileOnly": true,
    "transpiler": "ts-node/transpilers/swc-experimental"
  }
}

tsconfig.json

{
  "extends": "tsconfig.root.json"
}

If we use tsconfig.json with ts-node, currently it does not read "ts-node" field from tsconfig.root.json though extended.

@blakeembrey
Copy link
Member

IIRC it’s unfortunately due to the TypeScript API here - I don’t think we can get access to the extended definitions to be able to merge it. We should be able to file an issue in TypeScript to request support in the most recent version.

@cspotcode
Copy link
Collaborator

See also: #1292
The comments talk about implementation.

If you'd like, feel free to pick up that PR where it was left off. I can help explain anything that's confusing.

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

Successfully merging a pull request may close this issue.

3 participants