-
Notifications
You must be signed in to change notification settings - Fork 39
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
SyntaxError: The requested module '@agoric/nat' does not provide an export named 'Nat' #601
Comments
I agree the error message is cryptic. Exactly what steps does it take to reproduce it? I get a different message:
This problem is also noted in Agoric/agoric-sdk#3857 (comment) ; I was going to mark this one as a dup, but the scope of that one is more broad. |
running again, i'm not running into this error running the cli, however i'm pretty sure that it usually boils down to a package.json missing the following property: |
This error message is out of scope since it isn't really an Agoric error message. If it was easily reproduced, I'd go ahead & document it anyways, but as it is, it doesn't seem worth the bother of documenting. |
Not an Agoric error message? I wonder what you mean by that or how folks are supposed to know. What they know is that they tried our tool and it spit out a diagnostic that doesn't help them diagnose the problem, which is that the version of node they're using is out of date. Maybe it's not a doc bug but a bug in agoric-sdk. |
Umm... yeah. Please ignore the "Not an Agoric bug" comment. I don't know what I was thinking. I blame "too much coffee". Removing the "wontfix" label until I can think of a more coherent justification why this shouldn't be fixed. |
most likely overtaken by events |
When trying to run "agoric" command from a command line which is not pointing to a minimal node v14 as mentionned in the documentation, this cryptic error is thrown.
This is especially relevant if you manage multiple node version with nvm and node 14 is not your default version.
Solution :
nvm use 14
(or install node 14) and this error disappearsThe text was updated successfully, but these errors were encountered: