hyrious

Because we didn't configure the [`manualChunks`](https://vitejs.dev/guide/build.html#chunking-strategy) option in vite.config.ts. By default vite leaves it as empty (i.e. the same as rollup's default behavior). You can treat that as bundled all...

I have used my [esbuild-dev](https://github.com/netless-io/flat/blob/7b3590c41a14274f93c4c3e3d6eb41ac79080864/web/flat-web/package.json#L84) in flat-web scripts. Another choice would be [esno](https://github.com/antfu/esno).

In fact, without any other tools you can just do: ```bash esbuild scripts/build.ts | node --input-type=module ```

@rikers Have you tried `--install-directory somewhere`? From my personal experience, don't apply "run as admin" to any programming tool on Windows/macOS, it is likely to break everything. Instead find the...

> but it also wouldn't make the scripts available on the path Yes, you're right. But installing to the same place as node.exe would also annoy many users when they...

Although %localappdata% is perfered, in fact they are almost the same thing. Let me explain the 2 folders quickly: Windows has a tiny feature that it can sync program data...

You can treat the css file in my repo to never have chance to be changed again unless GitHub itself changed some colors some day. It is still there because...

It looks like a babel bug, simple reproduction: ```js import { transformSync } from "@babel/core"; import typescript from "@babel/plugin-transform-typescript"; let source = ` // entry.ts export namespace smart_player_namespace { export...

babel/babel#14773

It's 2020. Now we should have ability to resolve this issue: - [nativeTheme.shouldUseDarkColors](https://www.electronjs.org/docs/api/native-theme)