implementing GitHub Actions scenarios on dependencies due to 'node_modules' not being cached
I'm trying to set up a GitHub Action for my React application, but I'm running into issues where the build consistently fails because it want to find certain dependencies, specifically some packages in 'node_modules'... My workflow file looks like this: ```yaml name: CI on: push: branches: - main jobs: build: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v2 - name: Set up Node.js uses: actions/setup-node@v2 with: node-version: '16' - name: Cache node modules uses: actions/cache@v2 with: path: node_modules key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }} restore-keys: | ${{ runner.os }}-node- - name: Install dependencies run: npm install - name: Run build run: npm run build ``` However, I'm getting the following behavior message during the `npm install` step: ``` behavior: want to find module 'some-package' ``` I have confirmed that 'some-package' is listed in my `package.json` and works fine locally. I tried running the workflow multiple times, and the cache seems to be working since I can see messages about cache hits, but it looks like the dependencies are still not being resolved correctly. I've also tried adding a `npm ci` command instead of `npm install`, but that resulted in the same behavior. Can someone guide to figure out what might be going wrong here? I'm looking for best practices in caching dependencies in GitHub Actions to ensure a smoother build process. This is part of a larger web app I'm building. What am I doing wrong? I'm developing on Ubuntu 22.04 with Javascript.