Skip to content

paths in tsconfig.json vs tsconfig.app.json #1

@AdditionAddict

Description

@AdditionAddict

Is there a way to not have to repeat custom tsconfig paths in tsconfig.json and tsconfig.app.json?

ng test is using compilerOptions.paths where const { compilerOptions } = require('./tsconfig'); in jest.config.ts forcing tsconfig.json to have a paths defined here.

npm start errors if paths is not defined in tsconfig.app.json

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions