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

npx rap doesn't work. Wrong package registered inside npx. #57

Open
AlithAnar opened this issue Sep 24, 2021 · 3 comments
Open

npx rap doesn't work. Wrong package registered inside npx. #57

AlithAnar opened this issue Sep 24, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@AlithAnar
Copy link
Collaborator

AlithAnar commented Sep 24, 2021

While trying to call npx rap a different app responds.

image

Are there any plans to revive rap package in npx registry (maybe with a different name) ?

How can I run this locally? I'm trying to call:

node --experimental-modules ./node_modules/.bin/rap

but got

Error: Cannot find package 'fs' imported from /Users/gpasieka/dev/my.livechatinc.com/node_modules/react-automation-profiler/lib/bin.js
    at Loader.resolve [as _resolve] (internal/modules/esm/default_resolve.js:82:13)
    at Loader.resolve (internal/modules/esm/loader.js:73:33)
    at Loader.getModuleJob (internal/modules/esm/loader.js:147:40)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:41:40)
    at link (internal/modules/esm/module_job.js:40:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

EDIT
I was able to run it locally using node 14+ :)

@rpivo
Copy link
Owner

rpivo commented Oct 11, 2021

After updates to the main branch this week --
If you run npm run build in the react-automation-profiler repo, it should create a lib folder. If you replace the lib folder inside my.livechatinc.com/node_modules/react-automation-profiler with this new lib folder, do you still get this error?

I'll see if I can reproduce that error locally.

EDIT oh -- is the issue that it will only run with Node 14+ ?

@rpivo rpivo added the bug Something isn't working label Oct 11, 2021
@AlithAnar
Copy link
Collaborator Author

Yep, that's the case. I tried to build it locally with node 12 and didn't work. Could you specify a node version inside engines field in package.json ?

@rpivo
Copy link
Owner

rpivo commented Oct 12, 2021

Interesting, that's a good idea. should probably try to make this work with node 12, but I'll add this field for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants