question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Type-checking errors aren't reported

See original GitHub issue

Since there are no instructions for running the plug-in within parcel I assume it is supposed to work automatically - is that right? - but for me it doesn’t.

My parcel --version is 1.9.0 but during installation I’m told “npm WARN parcel-plugin-typescript@1.0.0 requires a peer of parcel-bundler@^1.9.0 but none is installed. You must install peer dependencies yourself.”

Any ideas? I installed both with --global, then tried reinstalling parcel-bundler and parcel-plugin-typescript with --save-dev; this time I got v1.9.1 and the warning message did not appear, but when running .\node_modules\.bin\parcel there is no sign that the plugin is running, e.g. no type errors.

Other warnings did appear:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

Issue Analytics

  • State:open
  • Created 5 years ago
  • Reactions:1
  • Comments:12 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
muellicommented, Oct 24, 2019

the needs-repro can be removed, I suppose.

1reaction
Vipseycommented, Aug 8, 2018

@QuantumInformation Fixed it by adding: “parcelTsPluginOptions”: {}, to the tsconfig file. Now its able to parse correctly as expected 👍

NOTE: if you have a , on the last line in “compilerOptions” it breaks. Removing this comma, fixes the issue. https://stackoverflow.com/questions/201782/can-you-use-a-trailing-comma-in-a-json-object/201856#201856

Read more comments on GitHub >

github_iconTop Results From Across the Web

ESLint not reporting TypeScript compiler type checking errors
Unfortunately ESLint only reports errors from it's own linters, it does not report typescript compilation failures.
Read more >
Typescript `next dev` error reporting · Issue #14997 - GitHub
Running next build to do type checking is not required. tsc --noEmit (typescript compiler in check mode) is enough to do type checking...
Read more >
Netscaler reports error running .r (r-code) for Webspeed
Netscaler reports error running .r (r-code) for Webspeed: MIME type ('text/html') is not executable, and strict MIME type checking is enabled.".
Read more >
Improving TypeScript error handling with exhaustive type ...
Discover an improved method for handling errors in TypeScript that solves problems that arise from returning null and throwing try...catch.
Read more >
Testing Types | Guide - Vitest
Vitest will also print out type errors in your source code, if it finds any. You can disable it with typecheck.
Read more >

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found