Skip to content

#833 Add support for path mapping in tsconfig.json #842

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
wants to merge 2 commits into from

Conversation

mko
Copy link

@mko mko commented Feb 9, 2016

Note: In order for the path mapping to be successful, you must be using typescript@next as of February 9th, 2016.

It might be worth holding on to this PR until TypeScript has fully documented this feature, but I wanted to make sure others who might encounter this issue trying to use path mapping were able to fix it themselves if needed.

Additionally, I haven't had time to fully test this yet like I would like, but it cleared up the errors in Atom and the compilation appears to be working properly again.

mko added 2 commits February 9, 2016 13:41
@mko
Copy link
Author

mko commented Feb 9, 2016

Resolves #833 by allowing for baseUrl and paths in the tsconfig.json validator.

@mko
Copy link
Author

mko commented Feb 10, 2016

Scratch this PR for now. After further testing, it ended up revealing that getting path mapping working with atom-typescript is going to take more work than just enabling the new tsconfig.json objects.

@mko mko closed this Feb 10, 2016
@nycdotnet
Copy link
Contributor

Thanks for submitting this regardless. Hope we'll be able to support this soon.

@TypeStrong TypeStrong locked and limited conversation to collaborators Jan 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants