-
Type: Task
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 3.0.x
-
Story Points:5
Right now, whenever we do a full build of the Elements, we republish the npm packages with the same SNAPSHOT version. However, this doesn't work well if we're using package-lock.json, because there will be two hashes for the same version: the one in package-lock.json and the one in the registry, thus causing an integrity check. We must find a different approach to publish SNAPSHOT versions of our npm packages. Because of this, we're forced to use the --no-package-lock flag everywhere were we do an npm install.
- depends on
-
ELEMENTS-1194 Publish release candidates when merging
- Resolved
-
NXP-29268 Publish release candidates when merging on Web UI
- Resolved
- is caused by
-
NXP-26829 Merge Web UI and Elements Repositories
- Resolved
- is related to
-
NXP-26957 Allow mvn install to skip package-lock.json
- Resolved