silverwind
silverwind
> Let's add [Vitest](https://vitest.dev/) to our investigation. It has a comparable API to Jest, but may offer better support for ESM. I also believe it uses ESBuild under the hood...
I'd say `data:` protocol is fine and should be part of any reasonable CSP because a lot of frontend js/css uses `data:` uris for many purposes and they are kind...
Actually I think the original issue is invalid and `unsafe-eval` was never needed, only `data:` which is generally considered a "safe" source. I think the behaviour of `unsafe-eval` for `img-src`...
Imho, SVGs as static hardcoded `data:` in CSS is perfectly fine and safe on it's own but of course, inline SVG in HTML would be ideal, which I guess means...
Imho, refactor to react components, but make it generic, e.g. ``.
Seems the maintainers have no interest in removing these `node` dependencies, so I can recommend [minimatch](https://github.com/isaacs/minimatch) instead which while slower, has no `node` dependencies so works in all environments like...
> querySelector and querySelectorAll are great APIs, but are not necessarily "better" than the existing ones. Agree. For cases like single class, `querySelectorAll` is magnitudes slower then `getElementsByClassname` for example....
Should also detect cases where `Array.from` is used to shallow-clone, e.g. when [`unicorn/prefer-spread`](https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/prefer-spread.md) is disabled: ### Fail ```js const sorted = Array.from(arr).sort(); ``` ### Pass ```js const sorted = arr.toSorted();...
Rule `import/no-unresolved` raise false positive when there is no `main` field in the `package.json`
Could `exports` just be treated as an alias to `main` for the purpose of linting? Or maybe this module could just use either `require.resolve` which does not have the issue....