Shasum check fails for v0.104.1

[ayushmanchhabra]

Refs: nwjs/nw.js#8305

[jonlepage]

Sorry for polluting the wrong repo, andthx for your time.

I followed your advice.
I deleted the nw folder from my node_modules, then re-ran the npm i command.
It seems the SDK isn't included, which is rather puzzling me.
Unless my memory is failing me, the SDK should normally be present ?

---

So I went directly to the official website to retrieve it and place it into the node_modules folder.

---

I then proceeded to decompress it to match the same folder structure I'm used to at least if my memory serves me right.

---

Unfortunately, I still encounter an issue during the build process with:

		await nwbuild({
			version: "0.104.1",
			mode: "build",
			glob: false,
			flavor: "sdk",
			cacheDir: "./node_modules/nw",
			srcDir: srcDir,
			outDir: buildOutputDir,
			platforms: ["win"],
			arch: "x64",
			logLevel: "debug",
		});

[ INFO ] Getting NW.js and related binaries...
Error: SHA256 checksums do not match. The file nwjs-v0.104.1-win-x64/nw.dll expected shasum is 3189cdefdcb8ae51cbb2fbbe1c351f68ef21aaf318ec233322fb71ac0b44e752 but the actual shasum is cf1d30f5dc8641f5117ae9bb51c5674a51a091dd60a9c2402980fbdff47fb37f.
    at verify (file:///D:/Users/jonle/Documents/DEV/projets/LEPA-DIALOG/LSDE/node_modules/nw-builder/src/get/verify.js:49:19)
    at async get (file:///D:/Users/jonle/Documents/DEV/projets/LEPA-DIALOG/LSDE/node_modules/nw-builder/src/get/index.js:97:3)
    at async nwbuild (file:///D:/Users/jonle/Documents/DEV/projets/LEPA-DIALOG/LSDE/node_modules/nw-builder/src/index.js:96:5)
    at async buildNW (file:///D:/Users/jonle/Documents/DEV/projets/LEPA-DIALOG/LSDE/task/build-nw.js:385:3)
    at async main (file:///D:/Users/jonle/Documents/DEV/projets/LEPA-DIALOG/LSDE/task/build-nw.js:521:2)

---

I believe it’s because the SDK is not being automatically retrieved with
"nw": "^0.104.1-sdk", and I’m forced to fetch it manually,
which shouldn’t normally be the case, right?

thanks

[jonlepage]

ok, I’ve resolved the issue.
Actually, I had previously left an ambiguous note, and I’ll take this opportunity to ask the question now i am here! 😄

The SDK no longer downloads with npm i, even though we have "nw": "^0.104.1-sdk" correctly defined in the package.json.

It’s now mandatory to run
npm i --save-dev nw@sdk

Several years ago, I used a post-processing step after npm i that worked well:
"postinstall": "cd ./node_modules/nw && npm install --nwjs_build_type=sdk",

However, this no longer works today.

Is there a new recommended approach or new mechanism in place to automate this process and ensure the SDK is installed automatically when updating the NW.js version, rather than having to run npm i --save-dev nw@sdk manually each time dependencies are updated?

---

I use VersionLens to update my dependencies, including NW.js.
That's why I encountered these issues: I wasn't updating them using npm, but i just click on the version I want with this plugin and then run npm i to update all my dependancies.

https://marketplace.visualstudio.com/items?itemName=pflannery.vscode-versionlens

[ayushmanchhabra]

Will look into this soon, thanks for the detailed report and explanation.