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.

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

fix(middleware): Catch errors when loading a module (#3572) #3573

Closed
wants to merge 1 commit into from
Closed

Conversation

jehon
Copy link

@jehon jehon commented Nov 13, 2020

Fix #3572

@karmarunnerbot
Copy link
Member

Build karma 380 completed (commit 891635fc48 by @jehon)

@AppVeyorBot
Copy link

Build karma 2778 completed (commit 891635fc48 by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 379 completed (commit 891635fc48 by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 381 completed (commit 2b0c20184c by @jehon)

@AppVeyorBot
Copy link

Build karma 2779 completed (commit 2b0c20184c by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 380 completed (commit 2b0c20184c by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 382 completed (commit 3054fc50b0 by @jehon)

@AppVeyorBot
Copy link

Build karma 2780 completed (commit 3054fc50b0 by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 381 completed (commit 3054fc50b0 by @jehon)

@jehon jehon changed the title Catch errors when loading a module fix(middleware): Catch errors when loading a module (#3572) Nov 13, 2020
@AppVeyorBot
Copy link

Build karma 2781 completed (commit 1c220fa432 by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 383 completed (commit 1c220fa432 by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 382 completed (commit 1c220fa432 by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 384 completed (commit 5f389087bd by @jehon)

@AppVeyorBot
Copy link

Build karma 2782 completed (commit 5f389087bd by @jehon)

@karmarunnerbot
Copy link
Member

Build karma 383 completed (commit 5f389087bd by @jehon)

@jehon
Copy link
Author

jehon commented Nov 26, 2020

@johnjbarton Sorry to interrupt you, but could you have an (updated) opinion on this PR?
The basis is that, without this PR and actually, karma report success when there is a syntax error in a es6 test.

@jehon
Copy link
Author

jehon commented Dec 14, 2020

Could someone review this PR?
If some work need to be done, could it be said?
Thanks

@johnjbarton
Copy link
Contributor

Sorry for the long delay. I want to investigate the possibility of correcting any tests that fail with the error on both paths.

@jehon
Copy link
Author

jehon commented Dec 15, 2020

I did look into the failings tests, nothing important. It's just that it test the string, and that in need to be adapted. I can push it here if wanted.

But the problem is that the output would change for errors in normal scripts (here, I put a call to "nothing()":

Uncaught ReferenceError: nothing is not defined
ReferenceError: nothing is not defined
   at tests/failing-test.js:2:1

Instead of

ReferenceError: nothing is not defined
   at tests/failing-test.js:2:1

There is no difference with the "if".

@jehon
Copy link
Author

jehon commented Dec 18, 2020

Followup in #3585

@jehon jehon closed this Dec 18, 2020
@jehon
Copy link
Author

jehon commented Dec 24, 2020

Followup in #3605

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Failing to load a (esm) module does not fail the test suite
4 participants