Is there an existing issue for this? <li class="

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

thanks for the suggestion <a class="user-mention notranslate" data-hovercard-type="use

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Closing duplicate of <a class="issue-link js-issue-link" data-error-t

[BUG] NPM stopped creating node_modules/.bin folder about cli HOT 5 CLOSED

mykola-mokhnach commented on August 29, 2024 1

[BUG] NPM stopped creating node_modules/.bin folder

from cli.

Comments (5)

Sebastian-Webster commented on August 29, 2024 2

Hi @mykola-mokhnach, never mind, Node.js 22.5.1 has came out and fixes that issue. nodejs/node#53902 (comment)

from cli.

mykola-mokhnach commented on August 29, 2024 1

thanks for the suggestion @milaninfy

Unfortunately it is not so simple for this particular case to use another Node.js version as they are retrieved automatically based on the latest LTS snapshots:

jobs:
  prepare_matrix:
    runs-on: ubuntu-latest
    outputs:
      versions: ${{ steps.generate-matrix.outputs.active }}
    steps:
    - name: Select all active LTS versions of Node.js
      id: generate-matrix
      uses: msimerson/node-lts-versions@v1

  test:
    needs:
    - prepare_matrix
    strategy:
      matrix:
        node-version: ${{ fromJSON(needs.prepare_matrix.outputs.versions) }}
    runs-on: macos-latest
    steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v3
      with:
        node-version: ${{ matrix.node-version }}

We'd probably need to wait for the next node patch 🤷

from cli.

Sebastian-Webster commented on August 29, 2024 1

Hi @mykola-mokhnach, a quick workaround for that problem would be to set the node version manually like this:

jobs:
  test:
    strategy:
      matrix:
        node-version: [18.x, 20.x, 22.4.1]
    runs-on: macos-latest
    steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v3
      with:
        node-version: ${{ matrix.node-version }}

and then once the patch for Node.js comes out you can go back to using the node-lts-versions action

from cli.