Incompatible with Deno 1.13.0
See original GitHub issueIssue
Setup:
- Deno Version: 1.13.0
- v8 Version: 9.3.345.11
- Typescript Version: 4.3.5
- Opine Version: 1.7.1
Details
Deno updated error definitions which is incompatible with http_errors
(i suspect). Has been introduced in https://github.com/denoland/deno/pull/10702
The error message I get:
error: TS2416 [ERROR]: Property 'name' in type 'PartialReadError' is not assignable to the same property in base type 'UnexpectedEof'.
Type 'string' is not assignable to type '"UnexpectedEof"'.
name = "PartialReadError";
~~~~
at https://deno.land/std@0.69.0/io/bufio.ts:26:3
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Incompatible with `Deno@v1.13.1` (latest) · Issue #93
Running the example: $ deno run -Ar --unstable https://deno.land/x/webview/examples/local.ts Error: error: TS2345 [ERROR]: Argument of type ...
Read more >CHANGELOG.md | lume@v1.13.0
Changelog. All notable changes to this project will be documented in this file. The format is based on Keep a Changelog, and this...
Read more >Deno 1.13 Release Notes
Deno 1.13 stabilizes the native HTTP server, and introduces FFI, a streaming WebSocket API, the new self.structuredClone() function and ...
Read more >Compare Packages Between Distributions
Complete summaries of the Guix System and openSUSE projects are available. Note: In case where multiple versions of a package are shipped with...
Read more >react native app failed to run on emulator "Unfortunately ...
... "win32" is incompatible with this module. info "fsevents@1.2.9" is ... @typescript-eslint/parser@1.13.0" has incorrect peer dependency ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Going by https://github.com/denoland/deno/issues/11713#issuecomment-899049214 we might be lucky and will be resolved in Deno core in a patch release today. Upgrading the deps is still a good exercise to do.
PR is ready for
http_errors
(https://github.com/ako-deno/http_errors/pull/5), waiting for a merge. Once its done, I can propose a PR here with the deps upgrades.