I just purchased PV Blocks and created an install dir to test it. I ran npm install, this found several vulnerabilities so I can ran npm audit fix --force, this resolved the warnings. Then, I ran npm run serve and now I get a few errors listed below during the web pack compilation. Anyone have some ideas on how to proceed?
> primeblocks-vue@3.0.0 serve
> vue-cli-service serve
INFO Starting development server...
ERROR Failed to compile with 3 errors 10:00:54 AM
ESLint is not a constructor
You may use special comments to disable some warnings.
Use // eslint-disable-next-line to ignore the next line.
Use /* eslint-disable */ to ignore all warnings in a file.
error in ./src/components/ecommerce/checkoutform/CheckoutForm.vue?vue&type=script&lang=js
Module not found: Error: Can't resolve 'core-js/modules/es.regexp.dot-all.js' in '/Users/Work/Dev/Tools/Vue/primeblocks-vue-3/src/components/ecommerce/checkoutform'
Error: Child compilation failed:
ESLint is not a constructor
- child-compiler.js:169
[primeblocks-vue-3]/[html-webpack-plugin]/lib/child-compiler.js:169:18
- Compiler.js:551 finalCallback
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:551:5
- Compiler.js:577
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:577:11
- Compiler.js:1196
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:1196:17
- task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
- task_queues:65 runNextTicks
node:internal/process/task_queues:65:3
- timers:437 processImmediate
node:internal/timers:437:9
ERROR in ./src/components/ecommerce/checkoutform/CheckoutForm.vue?vue&type=script&lang=js (./node_modules/babel-loader/lib/index.js??clonedRuleSet-40.use[0]!./node_modules/vue-loader/dist/index.js??ruleSet[0].use[0]!./src/components/ecommerce/checkoutform/CheckoutForm.vue?vue&type=script&lang=js) 2:0-46
Module not found: Error: Can't resolve 'core-js/modules/es.regexp.dot-all.js' in '/Users/Work/Dev/Tools/Vue/primeblocks-vue-3/src/components/ecommerce/checkoutform'
@ ./src/components/ecommerce/checkoutform/CheckoutForm.vue?vue&type=script&lang=js 1:0-216 1:0-216 1:217-422 1:217-422
@ ./src/components/ecommerce/checkoutform/CheckoutForm.vue 2:0-63 3:0-58 3:0-58 6:49-55
@ ./src/router.js 730:11-73
@ ./src/main.js 12:0-30 63:8-14
ERROR in ESLint is not a constructor
ERROR in Error: Child compilation failed:
ESLint is not a constructor
- child-compiler.js:169
[primeblocks-vue-3]/[html-webpack-plugin]/lib/child-compiler.js:169:18
- Compiler.js:551 finalCallback
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:551:5
- Compiler.js:577
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:577:11
- Compiler.js:1196
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:1196:17
- task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
- task_queues:65 runNextTicks
node:internal/process/task_queues:65:3
- timers:437 processImmediate
node:internal/timers:437:9
1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)
webpack compiled with 4 errors
PrimeVue blocks build errors
Does anyone from support monitor this forum? I still have the same problem after trying to fix the problem. First I tried to getting rid of entire ecommerce folder since it caused a build error. Then, I had to update routes.js to eliminate all references to eccommerce components.
Now, I get the following error that doesn't point to any specific file in the primeVue blocks source code... Anyone have any ideas? Not sure how this is considered commercial paid software when it won't run out of the box without errors and you can't get support... seriously, i need someone from support to at least acknowledge the issue. Was considering buying a template but that's off the table since it seems likely I'd have similar issues but if anyone has some input to steer me or offer any input on whether the templates have same type of issues, let me know.
npm run serve
> primeblocks-vue@3.0.0 serve
> vue-cli-service serve
INFO Starting development server...
ERROR Failed to compile with 2 errors 1:36:51 PM
ESLint is not a constructor
You may use special comments to disable some warnings.
Use // eslint-disable-next-line to ignore the next line.
Use /* eslint-disable */ to ignore all warnings in a file.
Error: Child compilation failed:
ESLint is not a constructor
- child-compiler.js:169
[primeblocks-vue-3]/[html-webpack-plugin]/lib/child-compiler.js:169:18
- Compiler.js:551 finalCallback
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:551:5
- Compiler.js:577
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:577:11
- Compiler.js:1196
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:1196:17
- task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
- task_queues:65 runNextTicks
node:internal/process/task_queues:65:3
- timers:437 processImmediate
node:internal/timers:437:9
ERROR in ESLint is not a constructor
ERROR in Error: Child compilation failed:
ESLint is not a constructor
- child-compiler.js:169
[primeblocks-vue-3]/[html-webpack-plugin]/lib/child-compiler.js:169:18
- Compiler.js:551 finalCallback
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:551:5
- Compiler.js:577
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:577:11
- Compiler.js:1196
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:1196:17
- task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
- task_queues:65 runNextTicks
node:internal/process/task_queues:65:3
- timers:437 processImmediate
node:internal/timers:437:9
1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)
webpack compiled with 3 errors
Now, I get the following error that doesn't point to any specific file in the primeVue blocks source code... Anyone have any ideas? Not sure how this is considered commercial paid software when it won't run out of the box without errors and you can't get support... seriously, i need someone from support to at least acknowledge the issue. Was considering buying a template but that's off the table since it seems likely I'd have similar issues but if anyone has some input to steer me or offer any input on whether the templates have same type of issues, let me know.
npm run serve
> primeblocks-vue@3.0.0 serve
> vue-cli-service serve
INFO Starting development server...
ERROR Failed to compile with 2 errors 1:36:51 PM
ESLint is not a constructor
You may use special comments to disable some warnings.
Use // eslint-disable-next-line to ignore the next line.
Use /* eslint-disable */ to ignore all warnings in a file.
Error: Child compilation failed:
ESLint is not a constructor
- child-compiler.js:169
[primeblocks-vue-3]/[html-webpack-plugin]/lib/child-compiler.js:169:18
- Compiler.js:551 finalCallback
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:551:5
- Compiler.js:577
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:577:11
- Compiler.js:1196
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:1196:17
- task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
- task_queues:65 runNextTicks
node:internal/process/task_queues:65:3
- timers:437 processImmediate
node:internal/timers:437:9
ERROR in ESLint is not a constructor
ERROR in Error: Child compilation failed:
ESLint is not a constructor
- child-compiler.js:169
[primeblocks-vue-3]/[html-webpack-plugin]/lib/child-compiler.js:169:18
- Compiler.js:551 finalCallback
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:551:5
- Compiler.js:577
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:577:11
- Compiler.js:1196
[primeblocks-vue-3]/[webpack]/lib/Compiler.js:1196:17
- task_queues:96 processTicksAndRejections
node:internal/process/task_queues:96:5
- task_queues:65 runNextTicks
node:internal/process/task_queues:65:3
- timers:437 processImmediate
node:internal/timers:437:9
1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)
webpack compiled with 3 errors
-
- Posts: 560
- Joined: 23 Oct 2020, 09:28
Hi,
I have tried to take a build PrimeBlocks 3.0.0 but I didn't get any errors like you have. PrimeBlocks do not have specific webpack configuration and it seems the errors come from on your side. What is your setup, webpack configuration?
Also if you could use PrimeBlocks page viewforum.php?f=152, we could follow blocks issues easily.
Best,
I have tried to take a build PrimeBlocks 3.0.0 but I didn't get any errors like you have. PrimeBlocks do not have specific webpack configuration and it seems the errors come from on your side. What is your setup, webpack configuration?
Also if you could use PrimeBlocks page viewforum.php?f=152, we could follow blocks issues easily.
Best,
-
- Information
-
Who is online
Users browsing this forum: No registered users and 14 guests