Fixes: #55918
Followup to #7027
Backporting #7207 into v9.
JS is far too widely used to warrant its omission here.
Fixes #49.
Closes #39
Fixed a bug and released v1.1.2
Published v1 of this package
Published v1.0.0
"filterer" is weird, and "fn" is not very descriptive.
Published v1.20.5 with a bug fix.
Published v1.0.0
Published v1.0.0 of es-set.
Published v1.0.0.
Published v1.0.0
Use CreateNonEnumerableDataPropertyOrThrow whenever possible.
Fixes #1868. Closes #1869.
Fixes #2524
https://github.com/ljharb/ls-engines/commit/35ff2ded86ce68b9f17c9b5310835eccb6bcd8a3
Used common actions workflows.
reuse actions workflows
Matching the changes in https://github.com/tc39/ecma262/pull/2595, assuming that lands.
I could also hoist up the actualDeleteCount
logic, and get rid of the if/elseif/else chain entirely, but I'm not as convinced that one would be an improvement.
Noticed this while reviewing/implementing https://tc39.es/proposal-change-array-by-copy/#sec-array.prototype.toSpliced
Published an official polyfill
updated a ton of projects; see commits referenced here https://github.com/inspect-js/is-arguments/pull/38
updated a ton of projects; see commits referenced here https://github.com/inspect-js/is-arguments/pull/38
I assume syncItems
is meant to be asyncItems
here?
This allows me to build a tool that gets the lockfile's contents without touching the filesystem.
It seems that this document is inadvertently recommending that folks publish polyfills in stage 1, which is incredibly dangerous for web compat, rather than in stage 3, which is the appropriate time.
This PR does not change any stage advancement criteria; in spec lingo, it is editorial, not no...
I noticed in #41003 that the loop-slice logic in addNumericSeparator
could be done with a single regex replace.
I did not change the implementation of addNumericSeparatorEnd
because the logic is slightly different, but I can try to do that if desired.
See https://github.com/nodejs/node/pull/41097#issuecomment-997055761
It was a very explicit and intentional decision to differentiate an undefined
cause from an absent cause, so let's display it.
Closes #355.
Once tests pass, I'll merge this.
Doing this as a PR to make sure CI passes first.
Fixes #1.
cc @bakkot @michaelficarra
Tests don't seem to cover this, but this seems right to me?
@zkat @iarna: I would dearly love your input on this change; if this env var checking is good, then I can next replace npm config get prefix
with "searching .npmrc files", which will give nvm a huge performance boost.
If there's a more robust way to do these comparisons, I'm happy to switch to that.