One questions about the "noParse" options
twt898xu opened this issue · 1 comments
twt898xu commented
Version
5.0.8
Environment info
System:
OS: macOS 13.4.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Binaries:
Node: 14.16.1 - ~/.nvm/versions/node/v14.16.1/bin/node
Yarn: Not Found
npm: 6.14.12 - ~/.nvm/versions/node/v14.16.1/bin/npm
Browsers:
Chrome: 115.0.5790.170
Edge: 114.0.1823.55
Firefox: 116.0
Safari: 16.5.2
npmPackages:
@vue/babel-helper-vue-jsx-merge-props: 1.4.0
@vue/babel-helper-vue-transform-on: 1.1.5
@vue/babel-plugin-jsx: 1.1.5
@vue/babel-plugin-transform-vue-jsx: 1.4.0
@vue/babel-preset-app: 5.0.8
@vue/babel-preset-jsx: 1.4.0
@vue/babel-sugar-composition-api-inject-h: 1.4.0
@vue/babel-sugar-composition-api-render-instance: 1.4.0
@vue/babel-sugar-functional-vue: 1.4.0
@vue/babel-sugar-inject-h: 1.4.0
@vue/babel-sugar-v-model: 1.4.0
@vue/babel-sugar-v-on: 1.4.0
@vue/cli-overlay: 5.0.8
@vue/cli-plugin-babel: ~5.0.0 => 5.0.8
@vue/cli-plugin-eslint: ~5.0.0 => 5.0.8
@vue/cli-plugin-router: 5.0.8
@vue/cli-plugin-vuex: 5.0.8
@vue/cli-service: ~5.0.0 => 5.0.8
@vue/cli-shared-utils: 5.0.8
@vue/compiler-sfc: 2.7.14
@vue/component-compiler-utils: 3.3.0
@vue/web-component-wrapper: 1.3.0
eslint-plugin-vue: ^8.0.3 => 8.7.1
vue: ^2.6.14 => 2.7.14
vue-eslint-parser: 8.3.0
vue-hot-reload-api: 2.3.4
vue-loader: 17.2.2 (15.10.1)
vue-style-loader: 4.1.3
vue-template-compiler: ^2.6.14 => 2.7.14
vue-template-es2015-compiler: 1.9.1
npmGlobalPackages:
@vue/cli: Not Found
Steps to reproduce
The webpack config generated by vue-cli contains a "noParse" configuration like
noParse: /^(vue|vue-router|vuex|vuex-router-sync)$/
It doesn't seem to work, because webpack module requests are all absolute paths, it can't match the above regular
If anyone understands please let me know thanks
What is expected?
noParse config can be work
What is actually happening?
the default "noParse" config can't work
AdrianMatta15 commented
why are you so beautiful???!!!????