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.

Sign up for GitHub

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

Jump to bottom

why noLib: true is set in tsconfig.json? #407

Closed
keroxp opened this issue May 14, 2019 · 1 comment · Fixed by #416
Closed

why noLib: true is set in tsconfig.json? #407

keroxp opened this issue May 14, 2019 · 1 comment · Fixed by #416

Comments

@keroxp
Copy link
Contributor

keroxp commented May 14, 2019 •
edited

スクリーンショット 2019-05-15 2 39 12

I'm using type definition file generated by deno types > deno.d.ts while developing. But IDE shows many symbol errors as noLib: true is set in tsconfig.json. Why noLib: true is needed? Doesn't deno explicitly refer to esnext lib?
@kitsonk
Copy link
Contributor

kitsonk commented May 14, 2019

There was a change of behaviour in TypeScript 3.2 in regards to noLib and the tsconfig should be changed to remove that and be more like https://github.com/kitsonk/deno_example

@keroxp keroxp mentioned this issue May 18, 2019
Merged
@ry ry closed this as completed in #416 May 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: add exnext lib to tsconfig.json keroxp/deno_std
2 participants
@keroxp @kitsonk