-
-
Notifications
You must be signed in to change notification settings - Fork 538
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
Correct usage with TS2 and @types/node #179
Comments
Can you provide the versions you're using? |
ts-node@0.9.1 |
That would be why. You need to update. |
This is the PR (#150) that should have enabled support. Let me know if that fixes things for you. |
Here's a related issue also: #153. |
Seems the issue persist with 1.3.0, in |
@whitecolor Are you using Windows? Could be the same issue as #168 - I haven't resolved that yet. |
Yes i'm using windows, ts-node doesn't lookup typings in |
It works on Unix as far as I know, so it's not that. |
Hello, Windows 10 64 bit here. Using typescript 2.0.3 and ts-node 1.3.0 I got this working by using the Here is an example tsconfig.json I'm using to run mocha tests via npm with the following script:
|
That works. |
I've installed
@types/node
and ts2 beta (locally and globally)If I do
tsc path/to/file.ts
(ornode ./node_modules/typescript/bin/tsc path/to/file.ts
) it compiles ok, so no need in placing path to node typings infiles
. But ts-node requires it.I use
ts-node
usingregister
hook and can not find typings for node while run. So I have to place:"node_modules/@types/node/index.d.ts"
infiles
oftsconfig.json
and then it works.Is it expected? Why it should it be configured this way?
The text was updated successfully, but these errors were encountered: