-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
TypeError: require(...).requirePackage is not a function #2
Comments
Same here. I see that these are circular dependencies. Is this a new thing? |
Broke several packages I use as well |
cc @balupton how can we help with this? |
just spotted this |
looking into it |
if others can look into it too, that would be appreciated what node verison, and what npm version are people using? as I cannot reproduce it on my own machine. |
|
Would someone be able to do this for me:
|
I encountered this issue on Node 10.13.0 with NPM 6.4.1. I noticed this version bump in what appears to be the most recent commit with significant changes (from ~2 hours ago). Was there an API change with the |
Same error:
|
I saw the same as @yesmeck |
two changes:
|
I guess the reason is the circular dependencies. |
|
circular dependencies have been supported in npm since I think v2 or v3 I also can't seem to reproduce this on my end |
I've setup https://github.com/balupton/errlop-issue-2 which works fine for me Can someone setup a repo that fails |
You can try running the tests of https://github.com/bevry/istextorbinary, they also failed with the above error on my end. |
@balupton Your repo works fine for me too, but running |
I just traced down the dependency chain for my project. |
interesting, maybe it is due to how the package managers handle symlinks cross platform
|
I am on macos |
well there goes that |
I just made a fresh package to test something. {
"name": "temp",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"dependencies": {
"istextorbinary": "^2.3.0"
}
} const istextorbinary = require('istextorbinary');
console.log(istextorbinary('hello world'));
I got the same error on two node versions: Dependencies as listed in lock file/resolved in |
working on a release of editions right now that skips errlop's dependency on it, and will release new versions for both perhaps this is happening because there are multiple can someone gist their |
yarn.lock
Edit to clarify: I have encountered this with both yarn and NPM, so that is unlikely to be the cause. |
should function as a workaround for bevry/errlop#2
okay, been able to reproduce |
YOLO package updating XD |
alright, try |
gonna have a shower (is quite late in sydney), let me know if it resolved or not with the latest versions of |
Works for me now, thanks! |
Worked for me as well. Thank you! |
@balupton 👏 you are amazing. Thanks for spending time on this. |
fantastic, thanks everyone for the speedy reports, you were all fantastic in debugging this, good work. I'm off to bed! Sorry for the inconvenience. Happy holidays |
My app works fine a hour ago, but after a refresh npm install, I got this error, and I found that
errlop
was just released a new version. So I guess the new version of errlop has some breaking changes.The text was updated successfully, but these errors were encountered: