execa not working with github script

[CarlFMateus]

I have tried to use execa with github script following the documentation that github-script shows me, but deploying it doesn't work either using yarn or using npm.

This is the code that I am implementing in github actions

jobs:
  tests:
    if: startsWith(github.head_ref, 'feature')
    runs-on: ubuntu-latest

    permissions: write-all

    strategy:
      matrix:
        node-version: [16.x]

    steps:
      - uses: actions/checkout@v3
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v3
        with:
          node-version: ${{matrix.node-version}}
      - name: Install dependencies
        run: npm ci
      - run: npm install execa
      - name: Do you have a unit test?
        uses: actions/github-script@v6
        with:
          script: |
            const execa = require('execa')
            console.log(execa)

[timheerwagen]

I am encountering a similar problem. I start a node package with npx in a github action, in which an execa command is executed, and then get the following error message directly when I try to start this command: spawn turbo run build --scope=admin ENOENT or spawn npx turbo run build --scope=admin ENOENT. On local everything works.

Apparently it cannot find the spawn command.

I have found the following workaround, which is to add {shell: true} to the execa command. But I don't like this for reasons that are obviously shown in the documentation.

shell

We recommend against using this option since it is:

- not cross-platform, encouraging shell-specific syntax.
- slower, because of the additional shell interpretation.
- unsafe, potentially allowing command injection.

[ehmicky]

Hi @CarlFMateus,

This is a problem with your usage of github-scripts, not of Execa, since the problem you are describing would happen with any other dependency that is using pure ES modules like Execa. I would recommend continuing this discussion in actions/github-script#346 instead. The following issues might help you as well: actions/github-script#168 and actions/github-script#249. Notably the following comment might be your solution: actions/github-script#249 (comment)

@timheerwagen Your problem seems to be different, could you please open a separate issue? Thanks.

[CarlFMateus]

Thank you very much for the clarification.

[ehmicky]

Another thing: you might want to check https://github.com/actions/github-script#use-esm-import as well.