Required Npm Dependancy: Node-Sass missing bundler files for windows and linux.

[34638a]

@jairo-bc

hey mate,

Tagging you directly because it looks like you're the last to push on the repo.
Node-Sass for Bigcommerce v10 (every version) has not shipped up a windows or linux bundle to NPM for some reason.
Check the npm code tab and then go to "versions" folder to see what has been published.

Relevant links:
BC Node-Sass Fork: https://github.com/bigcommerce-labs/node-sass
NPM: https://www.npmjs.com/package/@bigcommerce/node-sass/v/10.0.2?activeTab=code

Currently not sure how to resolve in the meantime but trying to manually copy over the bundles from the github.

• Jordan

[jairo-bc]

@34638a Thanks for letting know! I think if npm doesn't get it from the registry it tries to build binary locally. Isn't happening or failing?

[34638a]

@jairo-bc

Not super sure in this case, I've just signed off for the day so I'll investigate more tomorrow. Thusfar the only thing I could find is that even the github repo is missing the files in the latest published build, 10.0.0 has all the latest files (something.build) in the tagged release but 10.0.1 and 10.0.2 start dropping items out of the final release.

For now I've manually created the win32-x64-137 folder and downloaded the build from github to insert manually into node packages and that made builds work again.

I'll take some screenshots and add them as a update tomorrow too.

• Jordan

[34638a]

@jairo-bc

Ok, so here's the update from this morning:

A fresh pull of cornerstone and adding the dependency of stencil-cli results in the following node-sass dependancy coming down with it.

Which when calling npx stencil bundle yields the following to console (Full file path minified with **LocalPath**):

file:///**LocalPath**/cornerstone/node_modules/@bigcommerce/stencil-cli/lib/ScssValidator.js:33
                throw new Error(
                      ^

Error: Missing binding **LocalPath**\cornerstone\node_modules\@bigcommerce\node-sass\vendor\win32-x64-127\binding.node
Node Sass could not find a binding for your current environment: Windows 64-bit with Node.js 22.x

Found bindings for the following environments:
  - OS X 64-bit with Node.js 20.x
  - OS X 64-bit with Node.js 22.x

This usually happens because your environment has changed since running `npm install`.
Run `npm rebuild node-sass` to download the binding for your current environment. while compiling css files from "**LocalPath**\cornerstone\assets\scss/theme".
    at ScssValidator.run (file:///**LocalPath**/cornerstone/node_modules/@bigcommerce/stencil-cli/lib/ScssValidator.js:33:23)
    at async BundleValidator._validateCssFiles (file:///**LocalPath**/cornerstone/node_modules/@bigcommerce/stencil-cli/lib/bundle-validator.js:383:9)

Node.js v22.19.0

These are the only files present on NPM and new ones are not being built locally.

• Jordan

[jairo-bc]

@34638a Did npm install run successfully on fresh cornerstone copy?

[34638a]

Npm install itself runs fine and node modules is created in the local working space fine. Those screenshots and error snip was from a fresh pull of master (latest tagged release). On Monday I can zip what I have locally and upload it to the sandbox store webdav for download.

Node env is v22 Windows 10x64.

• Jordan

[34638a]

Morning @jairo-bc ,

I'm reaching out to our enterprise contact at BC to forward you a email with all the details to grab a copy of the cornerstone zip from WebDav.
It's just been put into the content folder so I'd rather not share that link publicly.

Sent to the Australia Customer Success Team for forwarding.

Cheers,

• Jordan

[34638a]

Gday @jairo-bc ,

Just a update to close out this issue: "build-sass": "npm explore @bigcommerce/node-sass -- npm run install" is the line I added to my package.json scripts list to be able to rebuild the SASS manually if needed. Does BC accept new scripts being added to the bin folder because if that's the case I can throw one together to trigger this as a PR.
If not then this is a closable issue.

Cheers,

• Jordan