silverwind
silverwind
If `full_bin` is changed to an array form, `cmd` would be last remaining option that takes string form. I wonder if you plan to unify these so all will only...
Hmm I think ideally pure unparsed shell command passed as a single string to the current shell would be the most flexible, consider this example from one of my apps:...
If I were to redesign this, I would only have two options, a `build` command and a `run` command, both accepting either an a array of command strings or a...
> we might want to specify ^0.25.0 || ^0.26.0 || ^0.27.0 or some such thing No you can not do that anyways because minor v0 versions are considered incompatible to...
Yeah I think ultimately esbuild it to blame that they are still on `v0`. They do release their changes as breaking but effectively, esbuild changes are rarely actually breaking. So...
A limited form of this exists at https://github.com/github/eslint-plugin-github/blob/main/docs/rules/no-dataset.md. I would welcome a better version of that that handles replacement with `getAttribute`, `setAttribute`, `deleteAttribute` and possibly also `hasAttribute`. Last one might...
This might be a non-issue when using https://www.typescriptlang.org/tsconfig/#verbatimModuleSyntax in Typescript, which would flag the missing `import type` statement for the second example. I think it's good practice to force `import...
I'd expect 90%+ users to be on a evergreen browser, but yes, those remaining 10% are a pain.
Just noting here that should we ever upgrade to tailwindcss v4, `color-mix` is in their [requirements](https://tailwindcss.com/docs/upgrade-guide#browser-requirements), thought I doubt much if anything would break if a browser doesn't have it.
https://tailwindcss.com/blog/tailwindcss-v4 Seems rather unexciting to me. Container queries might be useful, but other than that, it's a big breaking change that requires migration (maybe automated). Not the mention the weird...