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

SyntaxError: The requested module '@agoric/nat' does not provide an export named 'Nat' #601

Closed
HadrienPierart opened this issue Dec 25, 2021 · 6 comments

Comments

@HadrienPierart
Copy link

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 disappears

@dckc
Copy link
Member

dckc commented Dec 25, 2021

I agree the error message is cryptic.

Exactly what steps does it take to reproduce it? I get a different message:

$ agoric
/.../agoric-sdk/packages/agoric-cli/src/entrypoint.js:5
import '@agoric/install-ses/pre-bundle-source.js';
^^^^^^

SyntaxError: Cannot use import statement outside a module

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.

@tgrecojs
Copy link
Contributor

tgrecojs commented Jan 7, 2022

running agoric on it's own doesn't get me into this situation, but i have seen it a handful of times (just ran into it moments ago while walking through the process of configuring eslint with the jessie plug-in noted in the docs)

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: type: "module". looking at the stack trace of the error @dckc is getting leads me to believe that packages/agoric-cli might be missing this property assignment 🤔

@Tyrosine22
Copy link
Contributor

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.

@Tyrosine22 Tyrosine22 self-assigned this Jan 10, 2023
@dckc
Copy link
Member

dckc commented Jan 10, 2023

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.

@Tyrosine22
Copy link
Contributor

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.

@dckc dckc added link-sdk predates installation from npm; regards agoric install style and removed link-sdk predates installation from npm; regards agoric install style labels Dec 22, 2023
@dckc
Copy link
Member

dckc commented Dec 22, 2023

most likely overtaken by events

@dckc dckc closed this as not planned Won't fix, can't repro, duplicate, stale Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants