Bjorn Lu

Results 36 issues of Bjorn Lu

### Description fix #9334 Arrange `script type="importmap"` as first in `transformIndexHtml`. ### Additional context Needed this for dev external tests 🙂 --- ### What is the purpose of this pull...

feat: html
p3-minor-bug :hammer:

### Description `terser` is only needed if we're rendering legacy chunks. If `renderLegacyChunks: false`, we don't need terser as the existing code also actually doesn't need it, per https://github.com/vitejs/vite/blob/5f50693d515861eca971174cf9b860059132a58b/packages/plugin-legacy/src/index.ts#L349-L360 where...

plugin: legacy
p2-nice-to-have :cake:

### Description fix #6007 Introduce `__vite-optional-peer-dep` prefix (similar to `__vite-browser-external) for packages that are optional peer dependencies. ### Additional context Since knowing optional peer dep requires traversing the parent for...

p3-significant 🔨

### Describe the bug CSS linked via `` is not processed by default after #6751. I think it's still good as we provide a way for this to work with...

bug
feat: css

## Changes Fix #4093 Fix #4107 - `compat: true` now `noExternal`-ize all react entrypoints so Vite can process and alias them to preact compat - Bump to Vite `^3.0.5` to...

framework-preact
integration
core

Trying to dispatch a `new CustomEvent` without warning. Not sure if we need to add [the other types of events](https://developer.mozilla.org/en-US/docs/Web/API/Event#interfaces_based_on_event) to the list, it's probably rare to do a `new...

### Describe the problem Currently `sveltekit:prefetch` works by requesting data on hover or before click only. In some cases, it may be desirable to prefetch immediately when the link enters...

enhancement
p2-nice-to-have
prefetch

Reverts #1411 (and also #1439) Ref: https://github.com/vitest-dev/vitest/pull/1411#issuecomment-1151632260 It's not needed to remove type module to fix the issue stated in the PR

BREAKING CHANGE

## Changes Fix #502 I may be missing something big, but it doesn't seem like CSS needs to be escaped as it's not JS 🤔 I've removed it for CSS...

Repro: https://svelte.dev/repl/239f64a51b1448649b591b1522cef54c?version=3.31.2 When wrapping the `Boundary` component around any Svelte component, the errors aren't caught by `Boundary`. I'm not sure if this is a bug, or a limitation of this...