Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
The resource from “http://localhost:3000/users/css/style.css” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).
why is the '/users' being added to my link and why is this happening?
Hey all, has anyone looked at spinning each request off into it's own VM so you can use console.log anywhere in your app and have it prefixed with a unique request identifier?
Or is that a crazy idea?
@tomvisions, you can find quite a few examples on the official docs example page: https://expressjs.com/en/starter/examples.html
Additionally, mozilla has a fairly extensive tutorial on views and mvc-related contexts here: https://developer.mozilla.org/en-US/docs/Learn/Server-side/Express_Nodejs/routes
I recall reading an issue where @dougwilson said he was really trying to get Express 5.0 released before the end of the year... does anyone know how that's going?
I am asking in case there's anything I can help with
to my knowledge, there's only one outstanding (major) issue that needs to be addressed before moving out of alpha: pillarjs/router#102
I have worked on it and, IMHO, it should be ready for merging - unfortunately, effort seems to have died out due to lack of communication/time from maintainers
Hi @euoia I ended up going to the emergency room right befire Christmas and so was unable to get the 5.0 beta released, but I did get a 4.x patch. I have received 4 security vulnerability reports in the interim and will need to triage / address / make some additional 4.x releases as soon as I am discharged before I can resume 5.x work. I hope that answers your question. Let me know if you would like any further information and happy new year everyone. Sorry for the set back and I think we can get 5.0 released before the end of January, as there is almost nothing left there. I pushed some more commits to the 5.0 branch but just didn't get to cut a new release off it yet.
hey @dougwilson, many thanks for the update and very sorry to hear about your personal situation; hope you're feeling much better now! With regards to the vulns: would there be someone else that could be taking a look at those in the meantime? I'm up for it, if you need a hand.
Hi @dougwilson, I really appreciate the update. When I was looking through the GitHub issues again I saw your comment about recovering from sickness, and I'm sorry to hear you've been unwell again. I am going to see if I can get a pull request together for expressjs/expressjs.com#1313 and would also be happy to look at security issues if it's of any help. I will read through pillarjs/router#102 and see if there's anything I can contribute there.
I've read through the pillarjs/router#102 issue - should I have a stab at updating the migration guide to mention these changes? https://github.com/expressjs/expressjs.com/blob/gh-pages/en/guide/migrating-5.md
I'm just looking at the description of callback functions here
Is there a reason the documentation doesn't use the term "request handler" or something like that? If you define a callback without a
next parameter, is it still considered a middleware?
All the examples in the middleware callback function examples have the next parameter https://expressjs.com/en/5x/api.html#middleware-callback-function-examples
The distinction being that middleware must call
next, and the handler function must come last
error handler, event handler, request handler, etc.
Would you say that's accurate?
1 reply
@nfantone I am just trying to understand the updated path-to-regexp documentation https://github.com/pillarjs/router/blob/27ca41b4aa9fce28948b96addbb8d8b67698dfa9/HISTORY.md
Where it says "would match" or "would result" does that mean it used to but no longer does?
1 reply
In terms of impact on Express, for migrating Express from 4 to 5, I need to look at changes between n path-to-regexp 3.2.0 and 6.2.0, is that right (I'm basing that on the change to package.json in https://github.com/pillarjs/router/pull/102/files)
1 reply