electrovir

Are there any workarounds to this, besides removing the `type` keyword, that don't require manually enumerating all exports?

For complex globs with negations I need to use two separate globs as a workaround. However due to #8233 not actually having been addressed, even this workaround doesn't work in...

Another use case of unassigned imports: When defining a web component in the browser (`window.customElements.define`) there's usually no need to import anything from that component's file. However, the side effect...

I guess it depends on how you define a bug. The auto-fix behaves contrary to how I expect it to. I'd consider that a bug 😅 (Also I'm not sure...

I agree, that's a reliable convention. What I disagree with is the idea that the `order` rule violates that convention. If a dev is using side effects where order matters,...

My workaround is to run `vite build` and then `vite preview`. When using just the dev server, I get duplicate `node_module` imports but the built output does not have this...

Another workaround: I added the specific duplicated node_module to the `optimizeDeps.exclude` option: https://vitejs.dev/config/dep-optimization-options.html#optimizedeps-exclude

permissions needed: ``` permissions: contents: read pull-requests: write ``` https://github.com/kentaro-m/auto-assign-action/issues/136#issuecomment-1619235502

permissions needed: ``` permissions: contents: read pull-requests: write ``` https://github.com/kentaro-m/auto-assign-action/issues/136#issuecomment-1619235502

I don't have heaps of images to test how performant this is, but I took the logic from https://github.com/lovell/sharp/issues/1067#issuecomment-580969548 and wrote a self-contained async function in TypeScript that will output...