Gary Gozlan
Gary Gozlan
> it's too early to deprecate the stylistic rules If you don't have a drop-in npm package ready to replace these rules, their removal shouldn't be part of the release.
> how about deprecating only rules handled by pretty printers (e.g. Prettier)? This is off-topic but Id say you would still need a plugin that cover the other 8 rules....
> Without depending on specific environments like IE9, is there a case reasonable to add the new rule? Chrome and Safari are also affected : - 4096: - [bug 312913](https://bugs.chromium.org/p/chromium/issues/detail?id=312913)...
@kimulaco thanks for tackling the oldest non-upstream bug.
Shouldn't this have the high-priority label ? This is in the top 10 issues if you sort by 👍
@nektro what's `anyvalue`? Is it dependent on another proposal?
This has the added advantage of freeing `_` for #5893 see [@Rocknest's proposal](https://github.com/ziglang/zig/issues/5893#issuecomment-769027502)
> If necessary, I think it's this syntax that should change, rather than the others. Id expect `...`.
still getting ```sh dyld: lazy symbol binding failed: Symbol not found: _posix_spawn_file_actions_addchdir_np … dyld: Symbol not found: _posix_spawn_file_actions_addchdir_np … Crash at 0x56A2561601000000 ``` on `bun upgrade` bun version : 0.1.7...
> `--no-config` 👍 (or `--no-cfg`) > `--only` 👎 (see https://github.com/stylelint/stylelint/issues/4331#issuecomment-1068983735)