Closed naris closed 10 months ago
We are also facing the same issue while upgrading jhipster version from 7.9.4 -> 8.0.0
ERROR! ERROR! Command failed with exit code 1: npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks Error: Command failed with exit code 1: npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks { shortMessage: 'Command failed with exit code 1: npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks', command: 'npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks', escapedCommand: 'npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks', exitCode: 1, signal: undefined, signalDescription: undefined, stdout: undefined, stderr: undefined, cwd: '/Users/sonalchandani/prosperos/catarina', failed: true, timedOut: false, isCanceled: false, killed: false }
We tried multiple things to work it around 1) followed steps mentioned in https://github.com/jhipster/generator-jhipster/issues/22495#issuecomment-1587806831 but it didn't work. 2) also tried to use node 16 as well but it still didnt work.
Please let us know what would be the fix for this issue.
@sonal-prosperos Can you try the migrate blueprint? You'll have to clone the repo and run npm ci && npm link
before running it. I was able to use it on my v7 project and it worked. See comments on this issue for more information.
I'll try this out and with update you π
@sonal-prosperos Can you try the migrate blueprint? You'll have to clone the repo and run
npm ci && npm link
before running it. I was able to use it on my v7 project and it worked. See comments on this issue for more information.
We had the very same issue and using that blueprint worked (we just installed the npm package, not cloning the repo) -> not throwing the mentioned errors. Still not yet done with the manual part of the upgrade process, as there were kind of a lot of conflicts in our customizations, but from the upgrade process point of view looking so far quite alright.
@sonal-prosperos Did you have any luck using the migrate blueprint? I'm going to close this assuming it worked. If it did not, please re-open.
@mraible, I have finally gotten a chance to attempt to migrate my project using the migrate blueprint, which I installed with npm install jhipster-primeng-blueprint, and it did not go well :( It failed with a weird error complaining about an \@ in the generated code for the welcome page that is no longer present in my project: `β successfully regenerated source application using JHipster 7.9.4 β applying prettier to source application ERROR! An error occured while running jhipster-migrate:migrate#prepareMigrateBranch ERROR! ERROR! Failed to load plugin '@typescript-eslint' declared in 'CLIOptions': Cannot find module 'typescript' Require stack:
61 | ->follow @jhipster on Twitter<-a | ^^^^^^^^^^^^^^^^^^^^ 62 |
63 | /li 64 | /ul
I have created a bug for generator-jhipster-migrate with this issue
@mraible, the jhipster-migrate tool does not work :( I created a bug in the generator-jhipster-migrate project. I have since found that if I generate a new project using jhipster 7.9.4, without any plugins, and then tried to migrate it with generator-jhipster-migrate and it fails due to an @ in the default welcome page of the generated code (for the twitter link)
ERROR! An error occured while running jhipster-migrate:migrate#prepareMigrateBranch ERROR! ERROR! Failed to load plugin '@typescript-eslint' declared in 'CLIOptions': Cannot find module 'typescript' Require stack:
61 | >follow @jhipster on Twitter</a | ^^^^^^^^^^^^^^^^^^^^ 62 | > 63 |
Are you using Node 16?
@mraible The problem is when attempting to migrate jhipster angular applications that angular doesn't like @ in the source files, especially html, and will fail if it encounters them. This happens when the migration process run prettier on the source code since the default welcome page includes @ jhipster as a link to twitter :(
I am using node v18.13.0
Overview of the issue
When I attempt to upgrade my project form jhipster 7.9.4 (which was originally started with jhipster 7.0.2 and upgraded many times) to jhipster 8.0.0, the upgrade fails with this message:
β Cleaned up project directory INFO! Regenerating application with JHipster 8.0.0 and generator-jhipster-primeng-blueprint8.0.0 ... INFO! npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks ERROR! ERROR! Command failed with exit code 1: npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks Error: Command failed with exit code 1: npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks at makeError (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/node_modules/execa/lib/error.js:60:11) at execaSync (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/node_modules/execa/index.js:201:17) at execaCommandSync (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/node_modules/execa/index.js:276:9) at UpgradeGenerator.spawnCommandSync (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/node_modules/yeoman-generator/dist/actions/spawn-command.js:24:16) at UpgradeGenerator._generate (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/dist/generators/upgrade/generator.mjs:124:29) at UpgradeGenerator._regenerate (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/dist/generators/upgrade/generator.mjs:142:14) at UpgradeGenerator.generateWithTargetVersion (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/dist/generators/upgrade/generator.mjs:372:22) at UpgradeGenerator.executeTask (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/node_modules/yeoman-generator/dist/actions/lifecycle.js:244:26) at env.queueTask.once (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/node_modules/yeoman-generator/dist/actions/lifecycle.js:218:56) at runLoop.add.once (file:///C:/Users/murwilso/AppData/Roaming/npm/node_modules/generator-jhipster/node_modules/yeoman-environment/dist/environment-base.js:381:23) { shortMessage: 'Command failed with exit code 1: npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks', command: 'npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks', escapedCommand: 'npm exec --no jhipster -- --with-entities --force --skip-install --skip-git --ignore-errors --no-insight --skip-checks', exitCode: 1, signal: undefined, signalDescription: undefined, stdout: undefined, stderr: undefined, cwd: 'C:\src\totalfact', failed: true, timedOut: false, isCanceled: false, killed: false }
Motivation for or Use Case
to upgrade jhipster to latest supported version
Reproduce the error
upgrade a jhipster project to 8.0.0
Related issues
Suggest a Fix
JHipster Version(s)
7.9.4 to 8.0.0 upgrade
JHipster configuration
.yo-rc.json TotalFact.jdl.txt totalfact.zip
JDL entity definitions
Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryBrowsers and Operating System