-
Notifications
You must be signed in to change notification settings - Fork 58
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
Broken on node v8 #45
Broken on node v8 #45
Comments
Converted to clean objects here: mscdex/io.js@3d8528d resolves aseemk#45
The newly default node 8.0.0 is incompatible with the require-dir package: aseemk/requireDir#45
The same thing happened to me. Thank you for your quick fix. |
I just sent a PR #48 for this issue |
Hi, |
Also, regarding the use of https://nodejs.org/api/globals.html#globals_require_extensions What alternatives do we have? for (ext of Object.keys(require.extensions)) {
// ...
} would at least eliminate the use of |
Patch: #46 |
Mind my implementation with |
Hm when goes this fix live? :( |
Sorry folks, I've changed jobs and don't have time to maintain this library right now. I'm happy to add people as contributors — please just respect semver and get some amount of consensus before making major changes. =) Anyone interested in maintaining? cc @scragg0x and @krnlde — thank you both for the recent PRs! |
Okay, this is live on npm as 0.3.2. Thank you again @scragg0x and others for reporting and fixing, and for your patience! The offer to help maintain still stands for anyone interested. |
Btw, at my previous company (@fiftythree), we stopped using this package ( But! It looks like there's a proposal to support dynamic https://github.com/tc39/proposal-dynamic-import And it looks like that's being tracked or polyfilled by TypeScript, Babel, etc.: microsoft/TypeScript#12364 So maybe it'll be time for an |
@aseemk et al., thank you very much! I verified in my consumer that this is now working properly with both node 7.10.0 and 8.0.0 (previously failed with [email protected]). |
I would be interested in contributing/maintaining, we use this project heavily at my company. |
@stevelacy: Done! Thank you in advance for your help. =) |
update require-dir version to "^0.3.2" after module breaks in Node v8 (aseemk/requireDir#45)
Updating Require Dir version to 0.3.2 to fix issue with Node 8. See here: aseemk/requireDir#45
As suggested by aseemk/requireDir#45
I installed nvm (Node Version Manager) and downgraded node version from 8.8.1 to stable 6.11.0 and it resolved the issue. nvm install 6.11.0 |
Added next code on my machine instead of
Looks like working |
@faisalraza @fidelman This is a solved problem (for a long time) - just update |
@contra I tried about 7h ago, and I got
Node v8.10.0 |
@fidelman What are you using to install it? This module has Try clearing your cache and making sure you're getting the right version. |
As suggested by aseemk/requireDir#45
There appears to be a change in
require
in node v8 that breaks require-dir:Reported at: raineorshine/npm-check-updates#355
The text was updated successfully, but these errors were encountered: