-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] Fix introduced in #60 breaks backwards compatibility with old node.js versions #65
Comments
This is breaking me as well for a number of packages https://travis-ci.com/inspect-js/has-template-literals/jobs/292483820 v2 can't use |
@ljharb @pniewiejski we'll revert this to use |
Thanks! It’d be great to do it sooner, since all my packages’ CI is failing in the meantime unless i add a commit pegging the version of hosted-git-info. Perhaps you could make “latest” be 2.8.6 right now, so that people don’t have to get 2.8.7 unless they ask for it? |
…ssed node 6 support PR-URL: #66 Credit: @darcyclarke Close: #66 Reviewed-by: @darcyclarke
This should be fixed by #66 which was landed in |
What / Why
Changes introduced in #60 (specifically in commit: f2cdfcf) break compatibility for older versions of node.js which do not support
const
&let
variable declarations. Notice that inv2.8.7
, apart from one place in tests, it is the only place whereconst
(orlet
for that matter) is used in the whole project.So before #60 this project was backwards compatible and after #60 it is not. I think this should be considered a breaking change.
This fix (#60) was introduced between v2.8.6 and v2.8.7. Introducing breaking changes and bumping only the patch number is IMHO a practice that should be avoided.
Where / affected versions
Affected version is
v2.8.7
.node.js version:
0.10.*
(Yes, it's still there... 😢)Expected outcome
Change
const
declaration tovar
.The text was updated successfully, but these errors were encountered: