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.

Build fails with typescript 3.8.2

See original GitHub issue

Please paste the output of ember -v here

ember-cli: 3.16.0 node: 12.13.1 os: linux x64

Please paste the output of tsc -v here

Version 3.8.2

Please paste the version of ember-cli-typescript and ember-cli-typescript-blueprints here

├─ @glimmer/component@1.0.0 │ └─ ember-cli-typescript@3.0.0 ├─ ember-cli-typescript-blueprints@3.0.0 ├─ ember-cli-typescript@3.1.3 ├─ ember-concurrency-decorators@1.0.0 │ └─ ember-cli-typescript@2.0.2 └─ ember-load-initializers@2.1.1 └─ ember-cli-typescript@2.0.2

What are instructions we can follow to reproduce the issue?

yarn upgrade typescript@3.8.2
ember build
Reproduction Case

Updating typescript from 3.7.5 to 3.8.2 breaks the build. Downgrading again fixes it.

Now about that bug. What did you expect to see?

I can build the app.

What happened instead?

[Bundler]/my-ember-addon/node_modules/typescript/lib/typescript.js:98632
                throw e;
                ^

Error: Debug Failure.
    at Object.assertDefined (/my-ember-addon/node_modules/typescript/lib/typescript.js:2227:24)
    at /my-ember-addon/node_modules/typescript/lib/typescript.js:39435:34
    at Object.filter (/my-ember-addon/node_modules/typescript/lib/typescript.js:513:31)
    at serializeAsClass (/my-ember-addon/node_modules/typescript/lib/typescript.js:39433:48)
    at serializeSymbolWorker (/my-ember-addon/node_modules/typescript/lib/typescript.js:39164:29)
    at serializeSymbol (/my-ember-addon/node_modules/typescript/lib/typescript.js:39105:38)
    at /my-ember-addon/node_modules/typescript/lib/typescript.js:39080:25
    at Map.forEach (<anonymous>)
    at visitSymbolTable (/my-ember-addon/node_modules/typescript/lib/typescript.js:39079:33)
    at symbolTableToDeclarationStatements (/my-ember-addon/node_modules/typescript/lib/typescript.js:38950:17)
⠹ building... [Bundler](node:25503) UnhandledPromiseRejectionWarning: Error: Debug Failure.
    at CommandCoordinator.dispatchResponse (/my-ember-addon/node_modules/stagehand/lib/command-coordinator.js:54:69)
    at CommandCoordinator.<anonymous> (/my-ember-addon/node_modules/stagehand/lib/command-coordinator.js:43:29)
    at Generator.next (<anonymous>)
    at /my-ember-addon/node_modules/stagehand/lib/command-coordinator.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (/my-ember-addon/node_modules/stagehand/lib/command-coordinator.js:3:12)
    at CommandCoordinator.messageReceived (/my-ember-addon/node_modules/stagehand/lib/command-coordinator.js:40:16)
    at ChildProcess.emit (events.js:210:5)
    at emit (internal/child_process.js:876:12)
    at processTicksAndRejections (internal/process/task_queues.js:81:21)
(node:25503) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:25503) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I think this is the actual issue at the core of #1101

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:6
  • Comments:11 (8 by maintainers)

github_iconTop GitHub Comments

3reactions
dfreemancommented, Mar 10, 2020

I’ve got this narrowed down to a relatively small reproduction in https://github.com/dfreeman/typescript-3.8-debug-failure, and bisected the 3.8-dev releases to find which one it started happening in.

I reported what I found on https://github.com/microsoft/TypeScript/issues/37015#issuecomment-597282990, which will hopefully be reopened (and likely shouldn’t have been closed in the first place), so we’ll see what happens from here.

3reactions
mydeacommented, Feb 25, 2020

Yes, downgrading to 3.7.5 works!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Documentation - TypeScript 3.8
error! A type-only import can specify a default import or named bindings, ... are being accidentally imported, but still make side-effect imports explicit....
Read more >
Build errors after updating to Angular 9 and Typescript 3.8.3
I have managed to fix this. The problem was that the visual studio was using the wrong version of typescript. Simply installing this...
Read more >
Announcing TypeScript 3.8 - Microsoft Developer Blogs
Lots of users prioritize tightening their iteration time over addressing the errors up-front. As an example, it's fairly common to build code ...
Read more >
TypeScript Compiling with Visual Studio Code
Another benefit of using VS Code tasks is that you get integrated error and ... You can also define the TypeScript build task...
Read more >
typescript - npm
Start using typescript in your project by running `npm i typescript`. ... TypeScript icon, indicating that this package has built-in type ...
Read more >

github_iconTop Related Medium Post

No results found

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