We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The npm repository field has github.com/expressjs/express, and similarly, the issue link points to previous github issue tracker.
repository
github.com/expressjs/express
The text was updated successfully, but these errors were encountered:
Express was never stored at that url. Prior to the strongloop acquisition it was under visionmedia.
visionmedia
I'm fairly certain this was an intentional change to the package.json
Sorry, something went wrong.
Are you suggesting that the links intentionally go 404?
@bananu7 Yes I believe he is referring to the discussions going on in #2844
npm info express@4.13.3 | grep homepage homepage: 'http://expressjs.com/',
npm info express@4.13.4 | grep homepage homepage: 'https://github.com/expressjs/express',
4.13.4 was released after Doug indicated he would not be working on Express any more while strongloop/IBM owned it.
0513655
dougwilson
No branches or pull requests
The npm
repository
field hasgh.neting.cc/expressjs/express
, and similarly, the issue link points to previous github issue tracker.The text was updated successfully, but these errors were encountered: