Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0047401POS2Corepublic2021-07-15 12:412022-05-12 09:57
Reportershuehner 
Assigned Tojarmendariz 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tojarmendariz
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0047401: npm ci fails with node 16.x/npm 7.x 'org.openbravo.core2@*' is not in the npm registry.
DescriptionAfter fixing issue 47399 npm ci still fails.

Problem is the 'npm ci' in pos2 module which apparently does not find our core2 module.
Maybe some detail of our 'Creating links for ...' has changed and is no longer working

Installing node modules in /home/huehner/ob/branches/pi_pos2_pg/modules/org.openbravo.pos2/web-jspack/org.openbravo.pos2
npm ci...
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/org.openbravo.core2 [^] - Not found
npm ERR! 404
npm ERR! 404 'org.openbravo.core2@*' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
Steps To Reproduce1.) Have issue 47399 fixes or worked around
2.) Have Node 16.x, npm7.x as described in 47399
3.) run npm ci
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on defect 0047399 closed jarmendariz npm ci fails with nodejs 16.x in openbravo custom script (preinstall) 
depends on feature request 0048870 closed jarmendariz Add support to Node 16/Npm 8 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2021-07-15 12:41shuehnerNew Issue
2021-07-15 12:41shuehnerAssigned To => Retail
2021-07-15 12:41shuehnerTriggers an Emergency Pack => No
2021-07-15 12:41shuehnerRelationship addeddepends on 0047399
2021-07-15 12:45dmiguelezResolution time => 1629496800
2021-07-15 12:45dmiguelezAssigned ToRetail => platform
2021-07-15 12:45dmiguelezStatusnew => acknowledged
2021-08-16 12:18AugustoMauchResolution time1629496800 => 1631656800
2022-02-01 08:05alostaleAssigned Toplatform => Triage Platform Base
2022-03-31 09:56AugustoMauchNote Added: 0136197
2022-04-06 14:56jarmendarizAssigned ToTriage Platform Base => jarmendariz
2022-04-06 14:57jarmendarizRelationship addeddepends on 0048870
2022-05-12 09:54jarmendarizStatusacknowledged => scheduled
2022-05-12 09:57jarmendarizReview Assigned To => jarmendariz
2022-05-12 09:57jarmendarizNote Added: 0137204
2022-05-12 09:57jarmendarizStatusscheduled => closed
2022-05-12 09:57jarmendarizResolutionopen => fixed

Notes
(0136197)
AugustoMauch   
2022-03-31 09:56   
Removing due date because it is a minor issue
(0137204)
jarmendariz   
2022-05-12 09:57   
This issue was already fixed with the changes of issue 48870 that fixes the peer dependency to point to a local file. However, this dependency is currently ignored as we are using the --legacy-peer-deps flag, that we will hopefully remove when solving 0049023