Ability to use debug AVA tests with a launch configuration
See original GitHub issueWhat is the Problem Being Solved?
When running tests with a launch configuration (as here) I get this error,
SyntaxError: The requested module '[file:///opt/agoric/agoric-sdk/node_modules/@babel/types/lib/index.js]()' does not provide an export named 'default'
That’s caused by import '@agoric/babel-standalone' in @endo/init/pre-bundle-source.js`. (That particular error goes away when I comment out that line.)
Description of the Design
This might be solved by https://github.com/Agoric/agoric-sdk/pull/4718 . I’ll check after that is merged.
Security Considerations
–
Test Plan
–
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
ava/debugging-with-vscode.md at main · avajs/ava - GitHub
You can debug your tests using Visual Studio Code. ... Now, with a test file open, from the Debug menu run the Debug...
Read more >Debugging AVA with VS Code is not that simple - Łukasz Nojek
Debugging in VS Code requires creating a Launch Configuration stored in the .vscode/launch.json file. VS Code documentation. A very long manual ...
Read more >Faster way to run, debug and view results of Ava tests
Use Wallaby to boost your productivity by running and debugging Ava tests in VS Code as you are writing your tests/code. Use Ava...
Read more >JavaScript: How to use WebStorm debugger with ava
Create run/debug configuration, type Node.js · Select your node interpreter · As node parameter insert your ava bin and parameter --verbose. For ...
Read more >How you can test your Node.js applications with Ava.js - Medium
The handy thing about Ava is that it allows you to run async tests, via async await ... For the sake of simplicity,...
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 Free
Top 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

We still need
@babel/types. Maybe you were thinkingast-types?Per https://github.com/Agoric/agoric-sdk/pull/4758, we no longer depend on
@agoric/babel-standaloneor for that matterrecast, therefore neither@babel/types. So that just leavesesminagoric-cli, which is becoming rapidly less necessary as we’ve migrated most if not all dapp deploy scripts to Node.js ESM (NESM).