Solved: "ionic start" already failing with 404 (node-sass not found)

Trying to get my first Ionic app to run following the tutorial. Installed ionic and cordova, but it crashes already when trying to set up an application template using ionic start myApp tabs

Downloading the starter seems to work fine, but the subsequent npm i fails after a while:

[ERROR] An error occurred while running npm i (exit code 1):

        > node-sass@4.5.3 install D:\Repositories\Commercial\\TestApp\node_modules\node-sass
        > node scripts/install.js

        Downloading binary from
        Cannot download "":

        HTTP error 404 Not Found

What is your ionic info output?

    @ionic/cli-utils  : 1.18.0
    ionic (Ionic CLI) : 3.18.0
    Node : v9.2.0
    npm  : 5.5.1
    OS   : Windows 10

    backend : pro

My guess is that the scripts simply contain an invalid dependency? The node-sass URL in the command line output indeed points to a resource that doesn’t exist (anymore).

You are using a node version that was released yesterday (or today, depending on your timezone). My guess is that this is not yet ready for that node version. You should install the TLS.

I just tried updating to the current version and got the error:
Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (59) For more information on which environments are supported please see: at module.exports (D:\Projects\stemapp\node_modules\node-sass\lib\binding.js:13:13) at Object.<anonymous> (D:\Projects\stemapp\node_modules\node-sass\lib\index.js:14:35) at Module._compile (module.js:641:30) at Object.Module._extensions..js (module.js:652:10) at Module.load (module.js:560:32) at tryModuleLoad (module.js:503:12) at Function.Module._load (module.js:495:3) at Module.require (module.js:585:17) at require (internal/module.js:11:18) at Object.<anonymous> (D:\Projects\stemapp\node_modules\@ionic\app-scripts\dist\core\bundle-components.js:6:16)

So yeah I would just downgrade your Node version. @hardcodet

Edit: After downgrading ionic works again for me

1 Like

Yeah, we suggest in our setup docs that folks install LTS version of Node for this reason.
The speed at which node can move/upgrades makes depending on Node9 pretty crazy.
Constant updates make it hard for libs that require native compilation (node-sass, node-gyp) hard to keep up with.

They do their best, but using the LTS version of node is your best bet.

1 Like

Downgrading did the job - thanks for the quick replies! :slight_smile: