-
Notifications
You must be signed in to change notification settings - Fork 342
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
Compatibility with npm v3.0.0: Cannot find module #462
Comments
Leaving this note here because npm's own documentation site relies on |
Hey @othiym23! Congrats on the launch. I actually just updated Connect and fixed this yesterday on the release-v0.18.1 branch, we should be tagging a new release of Harp tomorrow—all tests are passing on Node v4.1.0 and npm@3.3.3. |
Resolved! Thanks @othiym23. Great work on getting npm 3 launched. |
Any chance that new release will be cut soon? |
@benburton Hey, we’ve published a couple of version since then. The latest is v0.20.x, which works with Node v5 and npm@3. |
Thanks @kennethormandy! |
Low priority since npm@3 is still in beta.
Code in middleware.js attempts to reuse the
send
module from theconnect
module. But because the new version ofnpm
now has a flat structure for modules, relative paths referencingnode_modules
fail.npm
is now smart enough to handle duplicate dependencies, so we should just includesend
as a dependency and it'll dedup.The text was updated successfully, but these errors were encountered: