-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
module: fix regression in require ../ #145
Conversation
If this is a regression, what was the commit that introduced it? Can you update the commit log to mention it? Thanks. |
Fixes regression in require system that prevented loading relative packages via main property in package.json where the file is not index.{ext}. The regression was introduced in cfc1272.
73028eb
to
393b355
Compare
Ok, I have amended the commit log as well as the PR description. |
I was just about to dig into this after seeing it myself. From a quick look at the code, it looks like |
Fixes regression in require system that prevented loading relative packages via main property in package.json where the file is not index.{ext}. The regression was introduced in commit cfc1272. PR-URL: #145 Reviewed-By: Ben Noordhuis <[email protected]>
Thanks Evan, landed in 87357b9 and good catch! |
For posterity, the commit that landed the original regression was 36777d2. |
Fixes regression in require system that prevented loading relative packages via main property in package.json where the file is not index.{ext}. The regression was introduced in commit 36777d2. PR-URL: #145 Reviewed-By: Ben Noordhuis <[email protected]>
Oh, so it is. Amended in 78a7dc2. |
ah sorry about that |
…id_type napi: Buffer data argument should be void* instead of char*
Fixes regression in require system that prevented loading relative
packages via main property in package.json where the file is not
index.{ext}. The regression was introduced via cfc1272
An example of a package affected by this is
node-gyp
.