-
Notifications
You must be signed in to change notification settings - Fork 202
"Typescript: Build" (F6) does not ignore node_modules when told #832
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
Comments
@basarat are you able to reproduce this bug? |
As to excluding your node_modules dir., you might try changing it to But I think that you will either have to ...
... if you want it to not complain.... otherwise Typescript will be unhappy seeing imports of the files. Right? |
|
Well, to be honest I am not sure if this is a bug at all. I think we can close this. Sorry, I am new to this typescript topic. |
I am sure this bug exists 🌹 Haven't had time to look it though. PS: I find myself struggling to maintain this project |
Ohh, thats sad. Maybe you could ask one of the other contributers? |
related : microsoft/TypeScript#6964 |
Adding the following to tsconfig.json seemed to do the trick for me: "exclude": [
"node_modules"
]
|
I have the following tsconfig.json:
When I hit F6 (Typescript: Build) it is looking into node_modules and thowing a compile error.
In my case: node_modules/angular2/src/facade/promise.d.ts Cannot re-export name that is not defined in the module.
That should not happen cause I told him to ignore node_modules.
My guess is that atom-typescript hadles "F6 build" an other way than the other builds...
If you want to test it - I have just done the Angular 2 5-min Quickstart: https://angular.io/docs/ts/latest/quickstart.html
The text was updated successfully, but these errors were encountered: