Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

Repository Modernizer error

Avatar

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

Avatar

Correct answer by
Employee

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 @Deleted Account\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 @Deleted Account\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

Avatar

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

Avatar

Level 2
i do have the path

Avatar

Employee 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.

Avatar

Level 1

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

Avatar

Level 2

Yes, instead of running the unified tool, i followed these steps mentioned here: https://github.com/adobe/aem-cloud-service-source-migration/tree/master/packages/repository-moderniz...

Avatar

Correct answer by
Employee

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 @Deleted Account\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 @Deleted Account\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.