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

ERR_INVALID_ARG_TYPE #2

Closed
aaronmoodie opened this issue Jul 3, 2024 · 4 comments
Closed

ERR_INVALID_ARG_TYPE #2

aaronmoodie opened this issue Jul 3, 2024 · 4 comments
Assignees

Comments

@aaronmoodie
Copy link

Hi, I've installed the script and run through the setup. I was able to generate the files.json successfully, but I'm getting this error when I try npm run start:


> figma-export@1.0.0 start
> playwright test

TypeError [ERR_INVALID_ARG_TYPE]: The "parentURL" argument must be of type string or an instance of URL. Received an instance of Object
    at new NodeError (node:internal/errors:405:5)
    at throwIfInvalidParentURL (node:internal/modules/esm/resolve:937:11)
    at Hooks.resolve (node:internal/modules/esm/hooks:241:5)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:337:35)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:220:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:307:34)
    at Hooks.register (node:internal/modules/esm/hooks:138:51)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:168:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:807:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28) {
  code: 'ERR_INVALID_ARG_TYPE'
}
@alexchantastic
Copy link
Owner

I wasn't able to reproduce this myself, but it seems like others are running into this with an older version of node (v20.x.x).

What version of node are you running? I just tested with v20.15.0 and did not see this error.

@alexchantastic alexchantastic self-assigned this Jul 4, 2024
@aaronmoodie
Copy link
Author

I'm on v20.7.0. I'll update to the latest and try again.

@alexchantastic
Copy link
Owner

Yep, I just loaded v20.7.0 and got the error so it seems like updating node is the fix here. Let me know if you run into the issue after you've updated. 😃

@aaronmoodie
Copy link
Author

Updated to the latest and all working well. Thanks! 😄

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

No branches or pull requests

2 participants