Application is broken about beverage-starter-flow HOT 8 CLOSED

A quick look into this it seems that there are 2 versions of at least text-field 2.4.4 and 2.4.5 where the latter is found from node_modules/@vaadin/flow-deps/node_modules/@vaadin/vaadin-text-field even though this happens also for base-starter it doesn't fail on it. But I have had many instances with this same node_modules setup fail on for instance Grid registering twice.

from beverage-starter-flow.

Multiple components have text-field set as 2.4.4 when the actual text-field is 2.4.5

text-field:2.4.4 is defined for:

• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]

from beverage-starter-flow.

I was able to replicate this but I am not exactly sure what is the original cause for this error. I am able to get rid of it by:

• removing node_modules, webpack.config.js, webpack.generated.js, package.json, and package-lock.json
• $ mvn clean
• $ mvn install -U -DskipTests (this was required, removing files and cleaning wasn't cutting it)
• $ mvn jetty:run

Now it is up on its feet. I can attempt to replicate this again, somehow.

from beverage-starter-flow.

Well, the build fails on TC.
I guess it starts with clean maven local repo.
I don't remember whether js and json files come with project .
So the issue is either in this or it's weird if not .

from beverage-starter-flow.

As an additional note, there is a java warning from the scanner
[main] WARN dev-updater - Multiple npm versions for @vaadin/vaadin-list-box found: [1.1.0, 1.1.1]. First version found '1.1.0' will be considered. that also points to some misconfiguration in flow components

from beverage-starter-flow.

If I reset the project to origin/master I am able to get this problem. I'll have have the directory /target/frontend/node_modules and following vaadin-text-field versions:

node_modules/@vaadin/vaadin-text-field :: 2.4.4
node_modules/@vaadin/flow-deps/vaadin-text-field :: 2.4.5
target/frontend/node_modules/@vaadin/vaadin-text-field :: 2.4.5

Removing package-lock.json will not fix the situation. Running mvn clean install will still produce the same error.

Removing both package-lock.json and ./node_modules and then running mvn clean install will fix the issues. There will no longer be a folder /target/frontend/node_modules.

from beverage-starter-flow.

node_modules is not in the VCS, right ?

So the only thing which we need to fix it is commit a new package-lock.json file.
Or am I missing something ?
Then it should work with a clean project (without being built previously).

from beverage-starter-flow.

Sure. But this seems like something users will eventually run again.

from beverage-starter-flow.