Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Repository Modernizer error

sravs508
Level 2
Level 2

Hi Team,

 

I am running Repository Modernizer as referred here: https://github.com/adobe/aem-cloud-service-source-migration/tree/master/packages/repository-moderniz...

 

My source maven project is of archetype 19 and getting below error:

********** Executing Repository Modernizer **********
Restructuring Repository..
node_modules\@adobe\aem-cs-source-migration-repository-modernizerbasePath
    Error: ENOENT: no such file or directory, stat
    'node_modules\@adobe\aem-cs-source-migration-repository-modernizer\resources\all'
    Code: ENOENT


Has anyone came across this error?

1 Accepted Solution
davidjgonzalezzzz
Correct answer by
Level 5
Level 5

Try version 0.0.8+ of the repo modernizer plugin.

 

The prior version exhibited this symptom, and the way to work around it was to perform a non-global install of @adobe\aem-cs-source-migration-repository-modernizer in the same folder in which you're running the aio plugin from.

 

Ex.

$ cd project-to-modernize

$ npm i @adobe\aem-cs-source-migration-repository-modernizer

 

But that said, that was fixed in v0.0.8 so just upgrade to the latest version and you should be set.

View solution in original post

6 Replies
praveenjain
Level 4
Level 4

As this is a node JS error which means File does not exists.

Can you check once if in below path all folder exists or not, all folder contains one pom.xml and src folder.

'node_modules\@adobe\aem-cs-source-migration-repository-modernizer\resources\all'

 

Regards

Praveen

shelly-goel
Community Advisor
Community Advisor

@sravs508 

Try running npm update and also check config.yaml is well formed.

If this doesn't help, you could try re-installing node and npm.

Piy-Malik
Level 1
Level 1

I am getting the same issue. Are you able to find the solution to this?

davidjgonzalezzzz
Correct answer by
Level 5
Level 5

Try version 0.0.8+ of the repo modernizer plugin.

 

The prior version exhibited this symptom, and the way to work around it was to perform a non-global install of @adobe\aem-cs-source-migration-repository-modernizer in the same folder in which you're running the aio plugin from.

 

Ex.

$ cd project-to-modernize

$ npm i @adobe\aem-cs-source-migration-repository-modernizer

 

But that said, that was fixed in v0.0.8 so just upgrade to the latest version and you should be set.

View solution in original post