Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions
Tracking ECMAScript Proposals
A class is already a function - decorators explicitly allow the capability to replace the value being decorated (when it's a class decorator). It would be trivial to ban that, but that was a critical use case for the decorator proposal - a good and necessary practice, not a bad one.
Of course we have a way to disallow it - decorators explicitly supports that use case because TC39 believes it is NOT a bad practice. If we thought it was a bad practice it wouldn't be possible.
The decorators are an inseparable part of the "type name" - especially since they might replace the entire value wholesale.
Makes sense. Why isn't it welcome there?
I ran into an issue installing NVM on my Mac Book Pro. I appended the nvm install instructions with the command to fix the scenario I ran into.
@elyobo if we enabled the option, it would break on eslint versions older than the one that added it - so, it's a breaking change to do so. This means that there should be a "TODO" comment above the rule, describing it as semver-major, and what change to make - that way, when we next have a breaking change, I'll do a sweep through the comments for any rules that are waiting to be enabled.
Does that mean you don't even want to parse them, as opposed to failing loudly when they try to use them?
I would hope that Temporal is never patched by anything except a 262 and/or 402 compliant polyfill - custom calendars shouldn’t be injected into globals.
Will this include some way to permanently persist any failing test inputs?
You can't omit/prune react in this case, you have to link it as well, in both places.
I've still not resolved the issue, but I haven't heard further reports from citgm either, so maybe the issue's resolved itself? Either way, I'd prefer the issue to stay open for now.
--omit=peer only omits your direct peer deps, not the peer deps of deps (which must be present for those deps to work). In this case, react-text-mask requires react to be present to function. Since you've omitted both dev and peer deps, there's no react present, so npm is forced to try to install a react that satisfies that package's peer dep.
@fregante this isn't a multi-file rule (for which "put it in the import plugin" is a very reasonable response), so i'm curious why that's a reason not to accept it into the unicorn plugin? (i can't comment there, unfortunately)
Looks like the
BAREWORD regex hardcodes
\s in the regex, which means space characters can't be escaped by the current implementation.
It should indeed be able to find them; if it's not, please file a new issue. I wouldn't bother setting amd to true, though, if you're just checking require cycles.
What sort of contexts? I'm not sure it makes sense to add complexity to a package called "shell quote" for non-shell usage.
true. altho it's probably more likely that someone is using a multi-char escape sequence than that they're passing an array containing one item
@srsudar incorrect, it does support them.
Are there any shells where these things are off?
What form would you expect?
I can imagine a regular expression or a predicate function, but those could have unpredictable results - a simpler option is to accept an array of multiple strings, but that would break anyone who'd been passing in an array of a single character. However, I'd hope nobody is doing this.
ha, true enough.
i can reproduce the bug easily but i can't figure out how to fix it yet.