Results 25 comments of Eleven

When I use vite-plugin-html-template, I must use `optimizedeps.entries` to make the pre-build effective, eg: ```js { optimizeDeps: { entries: [ '/xxx/xxxx/index.html', '/xxx/xxxx/main.ts', ] } } ``` Otherwise, the following message...

Sometimes we generate certificates that are shared by the team during the development phase,It would be better to allow custom name.

version: [email protected] yarn v1.22.19 vite v3 When I install a new package, the folder of `dist/cjs/checkers/vueTsc/typescript-vue-tsc` will be removed automatically (the same as `dist/esm/...`), and then dev error. And, retry...

> I wrote a plugin to extract static assets in library mode: [vite-plugin-lib-assets](https://github.com/laynezh/vite-plugin-lib-assets) > > usage: > > ```ts > import libAssetsPlugin from '@laynezh/vite-plugin-lib-assets' > > export default defineConfig({ >...

> 可以参考 `examples` 文件夹中的 [配置](https://github.com/IndexXuan/vite-plugin-html-template/blob/main/examples/vite-mpa-project-non-standards/vite.config.ts) . > > README 文档中也有[相关说明](https://github.com/IndexXuan/vite-plugin-html-template#options)。 遇到相同的问题,必须有 `/public/index.html` 文件,才能正常运行 vite build。而将 html 文件指定到其它目录位置,运行 build 即出现该错误提示。 给出的 examples 和 README 说明,已尝试均不管用,版本:`[email protected]`、`[email protected]`

`**-**-per-line` is turned off by default in [eslint-config-prettier](https://github.com/prettier/eslint-config-prettier). - https://github.com/prettier/eslint-config-prettier/blob/main/index.js#L124 - https://github.com/prettier/eslint-config-prettier/blob/main/index.js#L126 - https://github.com/prettier/eslint-config-prettier/blob/main/index.js#L154 Make it impossible to customize the max attributes of each row, None of the following configurations...

> We don't consider compatibility with ESLint rules. But the offical provides `prettier/eslint-plugin-prettier` `prettier/eslint-config-prettier`, When a developer tries to use prettier as a plugin for eslint, we need to consider...

> No, they disable rules conflicts with Prettier, but Prettier don't care which rules conflicts with us. It seems that we should not use eslint and prettier at the same...

Hello, is there any conclusion?

The following method should solve the problem, e.g: ```js // vite.config.js (e.g) const { getBabelOutputPlugin } = require('@rollup/plugin-babel'); export default { build: { rollupOptions: { plugins: [ /** * Running...