Installation no longer works due to failing object.assign dependency

What happened?

Installation of quasar v1 no longer works via yarn nor npm, nor via the quasar cli.

% yarn add -D @quasar/app@2
yarn add v1.22.19
[1/5]   Validating package.json...
[2/5]   Resolving packages...
...
[3/5]   Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/object.assign/-/object.assign-4.1.4.tgz: incorrect data check".
info If you think this is a bug, please open a bug report with the information provided in "/Users/noeldacosta/repo/gitlab/netbuilder/common/utils-quasar/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

What did you expect to happen?

Should install without dependency failures.

Reproduction URL

https://codesandbox.io/s/github/quasarframework/quasar-codesandbox/tree/legacy-v1

How to reproduce?

yarn add -D @quasar/app@2

Flavour

Quasar CLI (@quasar/cli | @quasar/app)

Areas

Quasar CLI Commands/Configuration (@quasar/cli | @quasar/app)

Platforms/Browsers

Other

Quasar info output

`quasar info` --- command not found.

Relevant log output

No response

Additional context

A reproduction URL is not relevant to installation related problems. I’ve pasted in the basic template because this form insists on a URL.

[rstoenescu]

You can now safely upgrade to Node 14+ with Quasar v1. Updated docs banner and will be available on next deployment.

[geoidesic]

It would help greatly if we could use higher than v12 node. We are just about to upgrade to quasar v2 but at present our code base is broken, as of this week. Firstly because of the problem described by Yusef but also mysteriously by these errors:

Module parse failed: Unexpected token (16:20)
File was processed with these loaders:
 * ..***@***.***/app/lib/webpack/loader.transform-quasar-imports.js
 * ../../node_modules/babel-loader/lib/index.js
 * ..***@***.***/app/lib/webpack/loader.auto-import-client.js
 * ../../node_modules/vue-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|     },
|     bb() {
>       return this.b?.a;
|     }
|   }

 @ ./Index.vue?vue&type=script&lang=js& 1:0-331 1:347-350 1:352-680 1:352-680
 @ ./Index.vue
 @ ../router/routes.js
 @ ../router/index.js
 @ /Users/noeldacosta/repo/quasar-project/.quasar/app.js
 @ /Users/noeldacosta/repo/quasar-project/.quasar/client-entry.js
 @ multi (webpack)-dev-server/client?http://0.0.0.0:8080 (webpack)/hot/dev-server.js /Users/noeldacosta/repo/quasar-project/.quasar/client-entry.js

Very weird because we’ve been using optional chaining in our app for more than a year, on node v12 (which apparently doesn’t support it). I can’t reconcile this – it was working till yesterday. Now it’s just not. If you have any ideas about that they would be very welcome. We can’t begin the upgrade without a working code-base because we need to first install composition api support for Vue 2, then convert all our code before we can actually do the upgrade.

Tx, Noel

On 3 Dec 2022, at 17:54, Yusuf Kandemir @.***> wrote:

@rstoenescu https://github.com/rstoenescu after making these updates I found out v9 is needed for Vue 2.7 linting support. The problem is with eslint-plugin-vue v9 doesn’t support Node v12, but in our docs, we explicitly state using Node versions higher than 12 is not possible. https://v1.quasar.dev/quasar-cli/installation https://user-images.githubusercontent.com/6266078/205449240-5e3db438-9dd3-4225-9c85-c4eda22fe9c2.png I didn’t test it in detail, but yarn quasar dev, yarn quasar dev -m ssr, yarn quasar build, and yarn quasar build -m ssr all work fine on Node v16.18.1. We might need to update the docs and create-quasar to let people know about this situation. If they want to use linting with Vue 2.7, they must use Node 14 and above, which seems possible. I am not sure about the source behind Webpack 4 not supporting higher than Node 12.

— Reply to this email directly, view it on GitHub https://github.com/quasarframework/quasar/issues/15044#issuecomment-1336187338, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDMKK2QYWXT6SHQO5PZV4TWLNUJRANCNFSM6AAAAAASR6HJRY. You are receiving this because you authored the thread.