Build error on some Linux machines #154
Comments
Hi, Thanks for reporting.
What is the exact linux distribution and version that you are using? |
Same error, I'm unable to continue working with Quasar after upgrade to 0.17 version, now previous versions of Quasar doesn't works on my side.
|
@uno-de-piera When you say previous versions of Quasar, what are you referring to? This problem is under investigation. It's most likely related to some webpack packages not doing their job correctly. |
@rstoenescu: Thanks for the quick reply. Here are my distribution details:
I've also tried removing the lazy loading of Unfortunately I don't understand how all these elements work together, and wasn't able to identify the exact problem. Here is the error in case I run
|
I'm referring that the if I try to install quasar-cli 0.16.0 doesn't works, if I try to install quasar-cli 0.16.4 doesn't works etc, currently I stopped my developments with Quasar because I'm unable to I can uninstall Quasar 0.17.2, clean the yarn cache and reinstall Quasar 0.16.0, but the issue persists with any version. PD: Before update to 0.17.x all environments worked well, this issue appears after Quasar update, it's strange that affects to another versions, but it's true. Thanks for your help. |
@uno-de-piera Until I figure this out, delete node_modules AND yarn.lock or package-json.lock (depending on whether you use yarn or npm), set your quasar-cli dependency to 0.16.4 then yarn/npm install again. I am sorry for this trouble, but it is an outside problem, not generated by Quasar. We are looking for solutions. |
Thanks @rstoenescu, no problem, don't worry 👍, I have this issue reinstalling all global dependencies and generating a new application with quasar-cli.
I tried all possible options before open the issue but currently I don't know what more done :( No matter the installed version, same error. |
You should also remove the |
Your project local quasar-cli version does the work. It doesn't matter the global quasar-cli version installed (as long as it's v0.15+). The global quasar-cli installation is there to be able to quasar init a project folder and for convenience of typing "$ quasar ..." instead of adding npm run scripts in your package.json (global quasar-cli detects if in a Quasar project then defers to the locally installed quasar-cli version). So if you want to go back to v0.16 in your project, make sure your project's package.json quasar-cli points to 0.16.4. Thank you for your patience while we figure the v0.17 problem. |
@Akaryatrh thanks for your help, but I uninstalled quasar of my computer, if I execute the quasar command the response is that quasar not found, when I install quasar-cli in any of its versions and generate a new project the issue persist :( @rstoenescu just now I updated quasar-cli to 0.17.3 with same result
Thanks guys 👍 |
@uno-de-piera uninstalling |
I know @Akaryatrh , first I remove the project with rm -rf project and then create a new project :), but removing .quasar folder inside project and reinstalling I too have issues. |
Sorry, is normal this behavior?
I have installed globally quasar 0.16.0, but when I build and enter inside of the project, this contains a quasar app with 0.17.x, strange :( |
Now testing with 0.16.0
I understand that the problem is the vue-router, but I don't understand why appears now this problem :(, I tried to reinstall local dependencies after downgrade quasar to 0.16.0 with same results... |
Version 0.17.3 works at a different machine, with the same linux distro and kernel, but with a newer version of NodeJS (9.11.2 instead of 8.11.3)
|
@matheusb-comp Don't think the Nodejs version matters, as long as it's >= 8. My linux machines all work (different Nodejs versions on them) and can't reproduce the issue. The good news is that tomorrow @pdanpdan will share his linux machine where this problem can be reproduced. However, can you try with the same Nodejs 8.11.3 on the machine you said it worked? Just to be 110% certain it's not affected by Nodejs version. It shouldn't, but who knows... |
Working fine with NodeJS 8.11.3. Thanks for investigating this issue. |
So it's not the Nodejs version. So what do some linux machines have that others don't, generating this webpack + babel issue? Will try to find out tomorrow, but any help is appreciated. |
Can you guys try setting quasar-cli dep to "0.17.0-beta.33" and report if it still happens? Thanks. |
@rstoenescu no such issues with 0.17.0-beta.33 |
Seems like Webpack needs to explictly be told to exclude node_modules from Babel transpiling for certain Linux distributions
Released CLI v0.17.5 which has the Webpack workaround. Thanks for helping out! Seems like Webpack needs to explictly be told to exclude node_modules from |
Thanks for your help @rstoenescu but not working in my side, the webpack issue has been solved, but now I have a blank screen without errors... it's only happens executing the app with cordova, attached screenshots.
Without layout using the router-view If the app is executed on SPA mode
Works fine, attached screenshot Also, in the new version (0.17.5), if I selected framework: 'all' option on quasar.config.js the app crashes with the next error.
Thanks! |
I'm getting the same error of Issue #153 on version
0.17.2
, in a new project template.I believe the error comes from Babel, since they decided to remove the Stage presets as of version 7.0.0-beta.54, as stated in the
npm install
warnings below.However, even after running the babel-upgrade tool on my project,
quasar-framework
, andquasar-cli
, I still kept receiving the same errors.Software version
npm install
warnings:What did you get as the error?
Error when running
quasar dev
:What steps did you take, to get the error?
quasar-cli
Support IE
onquasar init <folder_name>
cd <folder_name> && npm install
quasar dev
The text was updated successfully, but these errors were encountered: