@quasar/app v1.7.4 released!

[rstoenescu]

https://github.com/quasarframework/quasar/releases/tag/%40quasar%2Fapp-v1.7.4

Upgraded deps: @types/express@4.17.6, @types/webpack@4.41.12, autoprefixer@9.7.6, cross-spawn@7.0.2, css-loader@3.5.3, fork-ts-checker-webpack-plugin@4.1.3, isbinaryfile@4.0.6, node-sass@4.14.0, semver@7.3.2, terser-webpack-plugin@2.3.6, vuex@3.3.0, webpack@4.43.0, webpack-bundle-analyzer@3.7.0, archiver@4.0.1, file-loader@6.0.0, log-update@4.0.0, ts-loader@7.0.1, url-loader@4.1.0

[altezzalab]

after upgrade to node 14 and quasar 1.7.4 i got the following warning when building in PWA and SSR mode

(node:66883) Warning: Accessing non-existent property ‘lineno’ of module exports inside circular dependency
(Use node --trace-warnings ... to show where the warning was created)
(node:66883) Warning: Accessing non-existent property ‘column’ of module exports inside circular dependency
(node:66883) Warning: Accessing non-existent property ‘filename’ of module exports inside circular dependency

[ssuess]

@altezzalab I have the same problem after upgrading node today (from 12 to 14), did you ever find a solution?

[s.molinari]

We recommend using Node 12 currently.

Scott

[ssuess]

ah ok, thanks. I will revert. Is there a page somewhere you can point me to that has all these kinds of environment recommendations?

[s.molinari]

https://quasar.dev/quasar-cli/installation

Scott

[ssuess]

Right, that is why I thought 14 would be ok, it is an even version. It might be more useful to just clearly state the supported, recommended version number(s) in the documentation to avoid any confusion.

[s.molinari]

The red underlined part is what is recommended. LTS changes with time, thus why only that is mentioned.

Scott

[metalsadman]

@ssuess one can check that in the node js site or via nvm which version is their Current LTS (as of writing 12.18.1).