Closed platosha closed 2 years ago
Thanks for using Vaadin! We appreciate your help and we’ll take care of this as soon as possible.
oh,i see.. this place needs to be modified after the recent split.. https://github.com/vaadin/platform/blob/master/hilla/pom.xml#L131
and one thing to mention here, do we need to separate the versions.json here too?
We don’t even have hilla-core
yet. Looks like separation is out of scope for this bugfix.
Describe the bug
After the platform pinned versions split, Flow frontend tasks take
vaadin-versions.json
orvaadin-core-versions.json
resources into use. Thedev.hilla:hilla
artifact was not updated accordingly yet.As a result, webpack fails to compile TypeScript views in a Hilla project because web components cannot be resolved.
Expected-behavior
dev.hilla:hilla
1.2-SNAPSHOT hasvaadin-versions.json
resource.Upon starting the development server with a Hilla project without prior
node_modules
installed, Vaadin components are automatically installed from npm.Reproduction
1.2-SNAPSHOT
version of the Hilla platform dependency. Alternatively, removenode_modules
in an existing up-to-date project.package.json
update and npm install tasks.System Info
Hilla 1.2-SNAPSHOT