Webpacker: There is no yarn integrity check anymore

Adopt changes from Webpacker 5.1.0

rails/webpacker#2518

Author: ledermann

.github/workflows/push.yml

@@ -65,7 +65,7 @@ jobs:
             ${{ runner.os }}-yarn-
 
       - name: Install Node modules
-        run: yarn install
+        run: yarn install --frozen-lockfile
 
       - name: Run Tests
         env:

config/environments/development.rb

@@ -1,9 +1,6 @@
 Rails.application.configure do
   # Settings specified here will take precedence over those in config/application.rb.
 
-  # Verifies that versions and hashed value of the package contents in the project's package.json
-  config.webpacker.check_yarn_integrity = true
-
   # In the development environment your application's code is reloaded on
   # every request. This slows down response time but is perfect for development
   # since you don't have to restart the web server when you make code changes.

config/webpacker.yml

@@ -6,7 +6,6 @@ default: &default
   public_root_path: public
   public_output_path: packs
   cache_path: tmp/cache/webpacker
-  check_yarn_integrity: false
   webpack_compile_output: false
 
   # Additional paths webpack should lookup modules
@@ -52,9 +51,6 @@ development:
   <<: *default
   compile: true
 
-  # Verifies that correct packages and versions are installed by inspecting package.json, yarn.lock, and node_modules
-  check_yarn_integrity: true
-
   # Reference: https://webpack.js.org/configuration/dev-server/
   dev_server:
     https: false