-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Future: Express 5 #374
Future: Express 5 #374
Conversation
need to change |
resolved "https://registry.yarnpkg.com/bytes/-/bytes-3.1.2.tgz#8b0beeb98605adf1b128fa4386403c009e0221a5" | ||
integrity sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg== | ||
bytes@3.1.1: | ||
version "3.1.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait for body-parser
stable release
resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.5.0.tgz#d1f5d71adec6558c58f389987c366aa47e994f8b" | ||
integrity sha512-YZ3GUyn/o8gfKJlnlX7g7xq4gyO6OSuhGPKaaGssGB2qgDUS0gPgtTvoyZLTt9Ab6dC4hfc9dV5arkvc/OCmrw== | ||
cookie@0.4.1: | ||
version "0.4.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait for express
v5 stable release
resolved "https://registry.yarnpkg.com/@types/mime-types/-/mime-types-2.1.1.tgz#d9ba43490fa3a3df958759adf69396c3532cf2c1" | ||
integrity sha512-vXOTGVSLR2jMw440moWTC7H19iUyLtP3Z1YTj7cSsubOICinjMxFeb/V57v9QdyyPGbbWolUFSSmSiRSn94tFw== | ||
|
||
"@types/mime@*": |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be gone when @types/express
get to v5
Too outdated, will make a new one |
Instead of #374 but non-breaking The express 5 beta 3 is fully operational and tested by community, but its release is delayed. The current issue is that it's also outdated comparing to v4.18.2, having nested dependencies of older versions. latest tracking issue: ``` expressjs/discussions#233 ``` previous one: ``` expressjs/express#5205 ``` Latest proposal: ``` expressjs/discussions#160 ``` Probably it will be ready in march 🤞🏽 (no, it's not) ``` expressjs/express#5111 (comment) ```
The corresponding PR of
express
:expressjs/express#2237
Related issue
https://github.com/expressjs/express/issues/5205