v0.37.5

🚨Code Modification Required (for projects previously on ^v0.37.3)

Patch Release

This release resolves nine issues:

• update webpack-cli; remove patch workarounds #3599 by @thedavidprice
• Fix Scaffold generator for validation field #3594 by @aggmoulik
• Router: Fix ParamType #3589 by @Tobbe
• Updated RWGqlError type to match ApolloError #3585 by @cjreimer
• changed import path for all-currentUser template #3578 by @teovillanueva
• adds support for ts/js files on setup auth #3567 by @esteban-url
• Fix MetaTags issue with fragments #3564 by @simoncrypta
• path params overridden #3538 by @facinick
• Replace transformValue with validation #3605 by @jtoar

How to Upgrade

Code Modification

Projects using Redwood v0.37.3 (or v0.37.4) included a workaround in ./package.json, which resolved an upstream bug from the webpack-cli dependency. Projects no longer need to "pin" the dependency @webpack-cli/serve to 1.5.2.

If your project has the following resolution, the following change must be made in ./package.json:

// ./package.json

{
  "private": true,
  "workspaces": {
    "packages": [
      "api",
      "web",
      "packages/*"
    ]
  },
  "devDependencies": {
    "@redwoodjs/core": "0.37.3"
  },
  "eslintConfig": {
    "extends": "@redwoodjs/eslint-config",
    "root": true
  },
  "engines": {
    "node": "14.x",
    "yarn": "1.x"
+  }
-  },
-  "resolutions": {
-    "@webpack-cli/serve": "1.5.2"
-  }
}

Upgrade Packages to v0.37.5 from v0.37.x

Run the following command within your App's directory:

yarn redwood upgrade

Troubleshooting

After making the following code modification and upgrading, you can confirm your project is using @webpack-cli/serve@1.6.0 by running yarn why @webpack-cli/serve.

Check your project by running yarn rw dev. If you encounter any errors with webpack (specifically @webpack-cli/serve), try the following steps:

1. you can manually remove any occurrences of @webpack-cli/serve@1.5.2 from `yarn.lock, or
2. delete your project's ./node_modules, then run yarn -f, or
3. if your issue does not resolve, delete ./node_modules and also delete yarn.lock. Then run yarn

If you need further help, please ask in our Forums via a reply to the v0.37 Release Announcement.