can't start ext-react-modern-boilerplate

[Kurara]

I can't start the ext-react-modern-boilerplate. On the main page it is written that DO NOT run npm start for each folder. Why?

So I tried to run npm install in the main folder with an error:

npm install

> undefined postinstall /.../ext-react
> lerna bootstrap

lerna notice cli v3.4.3
lerna info Bootstrapping 20 packages
lerna info Installing external dependencies
lerna ERR! npm install exited 1 in '@sencha/ext-react-conference-app'
lerna ERR! npm install stderr:
npm ERR! code E403
npm ERR! 403 Forbidden: @sencha/ext-d3@~6.6.0

Then if I go to the expecified folder of ext-react-modern-boilerplate I can install it but can't run it. First I have the error Ext is not defined even if I put it into package.json variables. Searching I found that maybe java version was the problem, so I installed version 8 (I think, I get it from oracle-java8-installer):

java -version
java version "1.8.0_191"

Now the error running npm start is different:

✖ ｢wdm｣: Built at: 2018-11-26 14:13:50
Entrypoint app = app.js app.js.map

ERROR in i [ext]: Cannot satisfy requirements for "font-awesome"!

ERROR in i [ext]:    The following versions cannot be satisfied:

ERROR in i [ext]:       theme-neptune: font-awesome (No matches!)

ERROR in i [ext]: Cannot satisfy requirements for "font-ext"!

ERROR in i [ext]:    The following versions cannot be satisfied:

ERROR in i [ext]:       theme-neptune: font-ext (No matches!)

ERROR in i [ext]: Cannot resolve package requirements

ERROR in 65
ℹ ｢wdm｣: Failed to compile.

I don't know what to do u.u I've been months trying to install new ext-react version with unsuccess

UPDATE:

Installing and uninstalling many times I managed to install it. Now the problem is:

Uncaught Error: Expected subtree parent to be a mounted class component. This error is likely caused by a bug in React. Please file an issue.
    at invariant (react-reconciler.development.js:52)
    at findCurrentUnmaskedContext (react-reconciler.development.js:1484)
    at getContextForSubtree (react-reconciler.development.js:9845)
    at updateContainerAtExpirationTime (react-reconciler.development.js:9902)
    at Object.updateContainer (react-reconciler.development.js:9936)
    at ProxyComponent.componentDidMount (ExtJSComponent.js:57)
    at ProxyComponent.componentDidMount (react-hot-loader.development.js:577)
    at commitLifeCycles (react-dom.development.js:15961)
    at commitAllLifeCycles (react-dom.development.js:17262)
    at HTMLUnknownElement.callCallback (react-dom.development.js:149)

[mgusmano]

you don't run npm install in each folder since we use lerna - which does an npm install for each folder in the packages folder

[mgusmano]

also, you need to have a login to access the packages like @sencha/ext-d3@~6.6.0

[Kurara]

It didn't work neither when I try to install in the main folder. I'm not able to update sencha at all. I wrote them but I had 0 solutions. I regret hardly of acquisting it. If you want I could link the sencha forum post where I explained one by one my problems.

[dustinmcmanus2]

@Kurara Sencha doesn't keep their master branch clean. It is always full of commits that break their entire solution. Following their documentation exactly will cause any user to end up like you did. It is very frustrating. Even worse, they do not tell you that is what they are doing (even when you ask them in support tickets), causing users to bang their heads in frustration wondering why their stuff won't work. Everything might be working one day, and then the next day you do an npm install and everything is broken. I git cloned the repo and did a git reset --hard b5c02e70c495687394448cd0b878a8576ab937dd to get to a working state and also locked down the dependency versions (shown below), and I have been running off that commit a while. What Sencha should be doing is keeping only valid, tested, working, release commits on the master branch with a continuous integration server that runs the steps at https://docs.sencha.com/extreact/6.6.0/guides/getting_started.html with a test that ensures there are no errors in the chrome developer tools after the build finishes, so that they can be alerted whenever someone broke their repo in such a way that users can no longer follow the getting started steps.

To close this issue, Sencha has two options:

1. Always keep the master branch git HEAD on a working release, as mentioned above (preferred).
2. Update the getting_started.html page in the ExtReact guides and the "To Use this repo 'as-is' (to run the demos on your local machine)" steps in the README.md of the git repository to include the following full git bash steps:
   npm login --registry=https://npm.sencha.com --scope=@sencha
git clone https://github.com/sencha/ext-react.git
cd ext-react
git checkout master
git reset --hard b5c02e70c495687394448cd0b878a8576ab937dd
   Open packages/ext-react-modern-boilerplate/package.json in a text editor and delete all ~ and ^ symbols in front of all the version numbers under the "dependencies" section.
   cd ext-react
npm install
cd packages/ext-react-modern-boilerplate
npm start

where b5c02e7 is the last commit where everything still actually worked. Even the latest tagged release 9bc49d7 on the https://github.com/sencha/ext-react/releases page is broken, so right now there is no way to know which commits in the repo will work.

In addition, the ext-react-gen npm package should always be kept in a 100% working state, producing 100% working applications at all times, which is not happening either.

[dustinmcmanus2]

@mgusmano Regarding my comments above, I have confirmed that the issues under the OP UPDATE section above occur when working on a Windows environment. I decided to try it on my personal MacBook because I have seen MacOS used in all the Sencha demos, and sure enough everything worked fine using the steps above with the release commit 9bc49d7 without edits to the package.json files. It is clear that you are only testing on MacOS. However, for my development environment, I need everything to work for Windows Server 2016, because we deploy to IIS for our customers. This has been quite a cause for confusion, but your customers who have been reporting these kinds of issues have been right and should not be ignored. I will create a new support ticket on this issue.