| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Review requested:
|
Sorry, something went wrong.
|
s/shcema/scheme in commit message. |
Sorry, something went wrong.
|
It should be scheme (or prefix), not schema. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM but should we also add a test that requiring this without the scheme throws?
Sorry, something went wrong.
|
@RaisinTen added a test, can you please re-approve? |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks, still LGTM
Sorry, something went wrong.
Sorry, something went wrong.
|
Is this not a breaking change? |
Sorry, something went wrong.
no, it is a bugfix. according to documentation:
|
Sorry, something went wrong.
|
I get that you can call it a patch, but it will be a breakage for anyone using is-core-module, including anyone using resolve. |
Sorry, something went wrong.
|
Anyone using it? Really? Don't they have to pass test/reporters to it? |
Sorry, something went wrong.
|
What i mean is, tooling based on resolve will consider the schemeless one a core module. So yes, they’d have to be requiring it, but it’s a pretty big assumption that nobody’s doing that already. |
Sorry, something went wrong.
So I checked is-core-module and found inspect-js/is-core-module@9d5341a from 3 weeks ago so it doesn't look like a lot of time passed and the breakage seems reasonable in this case to not require a major. On a different note next time you see this sort of bug or oddity please report it :] |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, I agree it makes sense to land this as a patch
Sorry, something went wrong.
|
@benjamingr the bug or oddity imo is that test requires the scheme, and the only rationale i was aware of for requiring it was that test might be something people are already using. test/reporters didn't seem like it had that rationale. |
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #47831 Fixes: #47828 Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jacob Smith <jacob@frende.me>
PR-URL: #47831 Fixes: #47828 Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jacob Smith <jacob@frende.me>
PR-URL: nodejs#47831 Fixes: nodejs#47828 Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jacob Smith <jacob@frende.me>
| Back | FazBrowse Home | New Git URL |
Fixes: #47828