Closed ThornWalli closed 1 year ago
This is very strange, I don't think it seems to be the cause of the plugin. But I can't be sure either. You can write the build code of vite and webpack separately in different js files, and then use node to run to avoid this problem
import { build } from 'vite';
import viteConfig from './vite.config.js';
const startBuild = async () => {
await build(viteConfig)
console.log('vite build done');
}
startBuild()
import webpack from 'webpack';
import webpackConfig from './webpack.config.js';
const startBuild = async () => {
await new Promise(resolve => webpack(webpackConfig, resolve));
console.log('webpack build done');
}
startBuild()
run:
"test-1": "node test-1.js && node test-2.js"
You can also try using gulp
to handle your build process
I will close the issue for now, I have now made separate test files for the different builds. (e.g. webpack.test.js
and vitest.test.js
)
There is then in each case a single Describe which is executed separately from the other.
Thanks for support 😉
I got the same issue now with Vue 3 cli and Webpack 5
Exactly the same error
if (isComponentUpdateFnIdentifier && parent.type === "VariableDeclarator" && node.type === "Identifier" && node.name === "subTree") {
Found that I still get a problem with this plugin when I build
webpack
andvite
in a node instance.Example a Vitest with two Describes for the respective Builds.
Example: https://github.com/ThornWalli/webpack-sub-style-test
Reinstall the project and then run the task
test-1
.One of the two builds runs, both together do not.