Steve Ross

We use [EnvKey](https://www.envkey.com/) y for this (granted it is a paid project but, it is super handy for managing environments)

@jairo-bc not a fix, but at least there might be some advanced warning that you need npm@6 would be to add an engines declaration to package.json ``` "engines" : {...

Open a new terminal and ensure you're on the same node version as your project. Uninstall the global version of stencil cli: 1. uninstall: `npm uninstall -g @bigcommerce/stencil-cli` 2. reinstall...

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...

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

> @AnirudhSingal91 Have you tried @steve-ross's workaround in [#768](https://github.com/bigcommerce/stencil-cli/issues/768) ? > > > #### Workaround for NPM 7.x > > ``` > > npm i -g npm@6 > > npm...

@AnirudhSingal91 you can try doing a cache clean after you downgrade to npm@6 with `npm cache clean --force` May help to post some more info about your environment. ie: windows...

You may also want to reinit stencil... I had to do that even though my project was on 3.5.0 OR ensure you have an apiHost in your `config.stencil.json` ex: ```json...

@r742davis I was just typing something like this up... BigC shouldn't introduce breaking changes in point releases. DEFAULT YOUR DAMN VARIABLES! ```js const apiHost = config.apiHost || 'https://api.bigcommerce.com'; ```

yeah, I think is a bug in stencil-cli that is defaulting the apiHost variable to the store url instead of the actual api endpoint