Error: perf.getEntriesByName is not a function on npx run
ibrahimcesar opened this issue · 8 comments
Expected Behavior
- Return report from the url provided
Current Behavior
- Throws error
perf.getEntriesByName is not a function
Possible Solution
- Didn't debugged
Steps to Reproduce (for bugs)
- Used the command
npx is-website-vulnerable <url> - Accepted install from npm
- Returns error with Usage
Context
❯ npx is-website-vulnerable https://www.nexojornal.com.br
Need to install the following packages:
is-website-vulnerable
Ok to proceed? (y) y
✔ Set up completed in 9.20 seconds!
[ ] Auditing...
Error: perf.getEntriesByName is not a function
Usage:
is-website-vulnerable https://www.google.com
❯ npx is-website-vulnerable https://www.google.com
✔ Set up completed in 6.35 seconds!
[ ] Auditing...
Error: perf.getEntriesByName is not a function
Usage:
is-website-vulnerable https://www.google.comYour Environment
- Library Version used:
- Node.js v16.0.0
- Npm v7.12.0
- macOS Big Sur 11.4 Desktop
npm install -g is-website-vulnerablehas the same problem
Thanks @ibrahimcesar, looking into it.
If you already have the fix in mind, happy to land a PR.
Thanks to you @lirantal ! Great tool! Thanks for the fast response! No pressure, and great work!
I'm using macOS too but on a previous version (10) which works ok here so I can't reproduce immediately:
No pressure, and thanks a lot for the report 😀!
Ok I was able to replicate this with Node.js 16 and npm7 🙃
Looks like it's Node.js 16 but I'm exploring further
:tada: This issue has been resolved in version 1.14.8 :tada:
The release is available on:
Your semantic-release bot 📦🚀
@ibrahimcesar latest version should work now with Node.js 16 (due to an indirect dependency on marky which was the issue).
You probably need to wait a bit for npx to pull in the new version from the registry, or just try it out and see if it's already working for you :)