How to clear yarn / npm cache, or remove *.lock files | Community
Skip to main content
V
vadi
September 15, 2021
Solved

How to clear yarn / npm cache, or remove *.lock files

  • September 15, 2021
  • 3 replies
  • 8949 views

So, currently my project does not commit yarn.lock to the repository.
And I have access to https://experience.adobe.com/#/@myproject/cloud-manager/home.html/program/00001 to perform deployment (Real URI is redacted).

 

Currently, the build is failing due to one of the npm dependencies major version has changed.

I am wondering if there's any way we can clear yarn cache or lock files from the platform.

 

Error Log (Redacted):

06:39:39,772 [Exec Stream Pumper] [INFO] info If you think this is a bug, please open a bug report with the information provided in "/build_root/build/someprogram2-p33333/ui.frontend/yarn-error.log".error An unexpected error occurred: "ENOENT: no such file or directory, lstat '/build_root/build/someprogram2-p33333/xps-react/node_modules/autoprefixer'".

 

Sorry if this has been asked before, I am fairly new to AEM.

Please kindly assist me.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Anny0505

@umesh_thakur ,

 

Download the source code to your local machine and try to build to replicate the issue in your local. Once you're able to replicate the issue in your local machine then you delete node module and re build the code.

If your build is success then you can raise support ticket to clean up the node module to solve the build issue.

 

Hope this helps you!!

 

Thanks!!!.

3 replies

Umesh_Thakur
Community Advisor
Umesh_ThakurCommunity Advisor
Community Advisor
September 15, 2021

try to delete your node module folder and run npm install command and see.

It should work fine.

UmeshThakur

    V
    vadiAuthor
    September 15, 2021

    Hi @umesh_thakur - Thanks for the response.

    The node_modules directories are not committed. So I assume when the build starts it shouldn't have any, right? Or is there anyway I can SSH to cloud manager and run the build manually?

      Asutosh_Jena_
      Community Advisor
      Asutosh_Jena_Community Advisor
      Community Advisor
      September 15, 2021

      Hi @vadi 

       

      Please raise a ticket to the support team and they will be able to delete the folder for you. We do not have SSH access to the system where we can go and remove the file.

       

      Thanks!

        Anny0505
        Community Advisor
        Anny0505Community AdvisorAccepted solution
        Community Advisor
        September 15, 2021

        @umesh_thakur ,

         

        Download the source code to your local machine and try to build to replicate the issue in your local. Once you're able to replicate the issue in your local machine then you delete node module and re build the code.

        If your build is success then you can raise support ticket to clean up the node module to solve the build issue.

         

        Hope this helps you!!

         

        Thanks!!!.

          V
          vadiAuthor
          September 21, 2021

          You're right, the issue intermittenly happens in my local, and somehow I missed this.
          Thanks!

          Terms & ConditionsAccessibility statement

          Loading footer...