-
Notifications
You must be signed in to change notification settings - Fork 4
NodeJSEnv run does not fail if an ESModule fails #17
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
Labels
bug
Something isn't working
Comments
gzm0
added a commit
to gzm0/scala-js-js-envs
that referenced
this issue
Jan 17, 2022
gzm0
added a commit
to gzm0/scala-js-js-envs
that referenced
this issue
Jan 17, 2022
gzm0
added a commit
to gzm0/scala-js-js-envs
that referenced
this issue
Jan 18, 2022
gzm0
added a commit
to gzm0/scala-js-js-envs
that referenced
this issue
Jan 18, 2022
gzm0
added a commit
to gzm0/scala-js-js-envs
that referenced
this issue
Jan 22, 2022
sjrd
added a commit
that referenced
this issue
Jan 22, 2022
Fix #17: Fail run in NodeJSEnv if ESModule fails
gzm0
added a commit
to gzm0/scala-js
that referenced
this issue
Jan 31, 2022
We need the fix to scala-js/scala-js-js-envs#17 and some API improvements in the test kit.
gzm0
added a commit
to gzm0/scala-js
that referenced
this issue
Feb 4, 2022
We need the fix to scala-js/scala-js-js-envs#17 and some API improvements in the test kit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How to reproduce in this repo: Change
Script
toESModule
in:scala-js-js-envs/js-envs-test-kit/src/main/scala/org/scalajs/jsenv/test/kit/TestKit.scala
Line 161 in 01b0e95
The test suite will now hang for NodeJSEnv.
The text was updated successfully, but these errors were encountered: