purescript-contrib / purescript-contrib/setup-purescript
Not working locally with act
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to simulate the workflow locally with act, but I am getting this error:
[CI/build] 💬 ::debug::finished caching tool
| Cached path /opt/hostedtoolcache/spago/0.20.9/x64, adding to PATH
| Fetching psa
| [command]/usr/bin/sudo npm install -g purescript-psa@0.8.2
| sudo: npm: command not found
I tried the default config, and even adding
- uses: actions/setup-node@v3
with:
node-version: latest
cache: 'npm'
before uses: purescript-contrib/setup-purescript@main it still happens.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the workflow with act using the linked default configuration and the setup-purescript action. Inspect the tool-installation step that runs sudo npm install; done means the workflow can run locally with act without the npm: command not found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, devops, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100