Stencil start gives stencil-cli out of date error

[AnirudhSingal91]

I'm trying to serve my cornerstone theme locally. I have the latest version of stencil-cli installed (v3.5.0). Im getting the error "not ok -- Error: Error: You are using an outdated version of stencil-cli, please run $ npm install -g @bigcommerce/stencil-cli"

ive tried reinstalling stencil-cli but it didnt help.

Expected behavior

Expected behaviour is upon running strencil start, my stencil theme should start getting served localy.

Actual behavior

I get error "not ok -- Error: Error: You are using an outdated version of stencil-cli, please run $ npm install -g @bigcommerce/stencil-cli"

Steps to reproduce behavior

run stencil start

[zvuki]

Please install 3.5.1.

[AnirudhSingal91]

Please install 3.5.1.

it gives the error "not ok -- Error: Could not fetch a list of the store channels: Request failed with status code 404" now

[bookernath]

More context here: https://developer.bigcommerce.com/changelog#publications/required-stencil-cli-version-set-to-3-5-0

[bookernath]

@AnirudhSingal91 if you're still seeing the issue on 3.5.1, can you try regenerating your CLI token from the control panel? Sorry for the inconvenience.

[AnirudhSingal91]

@AnirudhSingal91 if you're still seeing the issue on 3.5.1, can you try regenerating your CLI token from the control panel? Sorry for the inconvenience.

I regenerated the token. im still getting the error "not ok -- Error: Could not fetch a list of the store channels: Request failed with status code 404"

[r742davis]

@AnirudhSingal91 I'm getting the same exact error on stencil-cli@3.5.1 after updating and using new tokens:

not ok -- Error: Could not fetch a list of the store channels: Request failed with status code 403

[steve-ross]

It is silly that you FORCE AN UPDATE every time you release a minor version or point release. This has killed half my day (and seems to every time you decide to push a new version).

[zpaquette]

My team is seeing the same thing as @AnirudhSingal91 and @r724davis. We have tried updating, uninstalling and reinstalling with no luck. Does anyone have a solution or work around?

[steve-ross]

@zpaquette try updating your API key to include read access on store channels

[AnirudhSingal91]

@zpaquette try updating your API key to include read access on store channels

How does that work? Aren't stencil CLI token and API keys completely independent of each other?

[rossyoung5]

Please install 3.5.1.

To be clear, attempting to resolve this issue led me directly into this concurrent issue: #768

I had to spend the better part of today trying to figure out what versions of node, npm and stencil-cli work together with no clear guidance from any of the output from stencil-cli. Why was this a forced update, especially with it not working on the latest npm in node 12?

[MattPua]

I will mention for myself:

Ran into the outdated stencil cli error.

After uninstalling stencil-cli, globally and then installing it again globally on version 3.5.1, it still wasn't working via npm run start.

However,

running stencil init again and then stencil start seems to work fine for now. Not the greatest experience but at least I can get it running for the interim again.

[drmzio]

Having the same issue. Was working just fine yesterday. Tried uninstalling the CLI and reinstalling but get an error like Cannot find module 'mkdirp' :/

I'm on Node v12.22.1

Update: The workaround mentioned in #768 worked for me 👍

[HATECORO]

ye, me too ,fk bc

[HATECORO]

I updated BC,then let me update node ,fk ,wst my time .