DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.

[lucadalli]

[DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.
BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
        Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.
        Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.
(Use `node --trace-deprecation ...` to show where the warning was created)

vue create options

Vue CLI v5.0.1
? Please pick a preset: Manually select features
? Check the features needed for your project: Babel, TS, CSS Pre-processors, Linter
? Choose a version of Vue.js that you want to start the project with 3.x
? Use class-style component syntax? No
? Use Babel alongside TypeScript (required for modern mode, auto-detected polyfills, transpiling JSX)? Yes
? Pick a CSS pre-processor (PostCSS, Autoprefixer and CSS Modules are supported by default): Sass/SCSS (with dart-sass)
? Pick a linter / formatter config: Prettier
? Pick additional lint features: Lint on save
? Where do you prefer placing config for Babel, ESLint, etc.? In dedicated config files
? Save this as a preset for future projects? No

chrome-extension-cli options

✔  Successfully installed plugin: vue-cli-plugin-chrome-extension-cli

? Name of the Chrome Extension? chrome-extension-name
? Description for the Chrome Extension? chrome extension
? Version for the Chrome Extension? 0.0.1
? manifest_version for the Chrome Extension? 3
? delete Initial file? (src/main.js src/components public/index.html public/favicon) Yes
? Please select the required components : background, popup, content

[sanyu1225]

I try to upgrade my vue-cli to 5.0.1
Then create the same vue project
This situation did not occur
Can be normal npm run build
Can you provide node version for me to try?

[lucadalli]

@sanyu1225 My current node version is v16.13.1

I should clarify that the error appears when running npm run build-watch

[sanyu1225]

@lucadalli
OK, I found the problem. It is not affected for the time being because there is only a warning prompt.
It will be corrected in the next version