Roman Shtylman
Roman Shtylman
+1 Agreed. My longterm hope is that a package manager understands history.md or something and just grabs the version from that on publish.
If there is no version field in a json file then should it be ignored? (There might be json files that are unrelated to the package). I am skeptical about...
which files to whitelist then? package.json component.json any others?
Any desire to merge this?
use `make dist` to try it out
We decided against this because .use carries a specific meaning with what it does to req.path
I need to check on the OPTIONS behavior but I would lean towards making sure `.all` doesn't affect OPTIONS for `.route` or `app.all()` but that might break some other assumptions...
I think we should change `.all` to simply add middleware and not affect options responses. Yes, it will be slightly different than app.all, but whatever.
Sounds like a 5.x feature maybe. Along with possibly ripping out the routing system into a module finally.