Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: ENOENT #51

Closed
richardtapendium opened this issue Nov 19, 2020 · 4 comments
Closed

Error: ENOENT #51

richardtapendium opened this issue Nov 19, 2020 · 4 comments

Comments

@richardtapendium
Copy link
Contributor

richardtapendium commented Nov 19, 2020

When running this action, I am getting the following error:

/usr/local/bin/npx vercel --prod -t *** -m githubCommitSha=9c1a00cc9e604db43d6e0598ad26510a70c40f98 -m githubCommitAuthorName=richardtapendium -m githubCommitAuthorLogin=richardtapendium -m githubDeployment=1 -m githubOrg=tapendium -m githubRepo=tapendium-pwa -m githubCommitOrg=tapendium -m githubCommitRepo=tapendium-pwa -m githubCommitMessage=test -m githubCommitRef=refs/heads/vercel-deploy --scope ***

Error: There was an error when attempting to execute the process '/usr/local/bin/npx'. This may indicate the process failed to start. Error: spawn /usr/local/bin/npx ENOENT

My script looks like this:

name: deploy website
on: push
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: amondnet/vercel-action@v19.0.1+4
        with:
          vercel-token: ${{ secrets.VERCEL_TOKEN }} # Required
          github-token: ${{ secrets.GH_TOKEN }} #Optional 
          vercel-args: '--prod' #Optional
          vercel-org-id: ${{ secrets.VERCEL_ORG_ID}}  #Required
          vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }} #Required 
          scope: ${{ secrets.VERCEL_TEAM_ID }}
          working-directory: ./sub-directory

Any help is much appreciated.

@richardtapendium
Copy link
Contributor Author

Okay finally found the issue, just needed to remove the working-directory which was copied from the example.

@hassam7
Copy link

hassam7 commented Jun 4, 2021

I am encountering the same issue but I need the working-directory option. is there any workaround?

@dakshshah96
Copy link

@hassam7 Were you able to find a solution to this? I need the working-directory option too so I can deploy the dist folder after it's built.

@hassam7
Copy link

hassam7 commented Dec 12, 2021

@dakshshah96 😅 our project was given to other team. not sure whether they resolved the issue or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants