-
Notifications
You must be signed in to change notification settings - Fork 4
V11 starter does not start up when following /start instructions. #15
Comments
The readme of the starter contains |
It has been agreed long time that front-end starters should use P3, even though Vaadin platform does not support it yet. If for some reason someone really wants instructions for running React app with P2, instructions are available but not highlighted in the download button. Please follow up the issue |
It it generated from V10 and V11 branches, respectively. Please see #12 and #13 for description why we cannot simply use P3 versions for now. My opinion is that we should have a working Webpack config to be used with all the starters. Not sure how much are we ready to invest into this, for now I'm recommending users to use my own starter: I've put significantly more effort into it, both CF and personal evening coding, and I believe that is how the proper starter should look like. |
At least Right now there is a big inconsistency between instructions listed on the
Please switch the download to use the |
Once we release V12 with the official Polymer 3 support, we will be able to switch starters to use it in case if these issues are fixed by that time (some of those are related to React tools). |
Good, but for now, |
The zip file there is working, they should update starting instructions to match readme. |
Vaadin 12 still has few months to go. |
Fixed by #16 on the |
On https://vaadin.com/start/latest/react, the instructions to get the starter to use are the following.
yarn install
yarn start
Following these instructions, you get a huge error on your screen when it is loaded in the browser, and the app is unusable.
This can be fixed with an
bower install
between 3 and 4.Furthermore, the README.md has another list of instructions.
npm install
bower install
npm start
These instructions work out of the box.
Please choose one set of instructions that work, and put the same set in both the README and /start/latest/react
(and other versions than latest if they are broken as well).
The text was updated successfully, but these errors were encountered: