This release introduces the new
🎉
Redwood Auth Package
🎉
, which is a lightweight wrapper around popular SPA authentication libraries. Current support includes Netlify Identity Widget, Auth0, and Netlify GoTrue-JS. (With more on the way!) And it wouldn't be done the Redwood Way if it didn't include a generator to handle the boilerplate for you. We hope you find it delightful to use!

Breaking
⚠️

For previously deployed applications, it is possible the new Prisma migration files from beta.5 are incompatible with previous migrations. If you encounter a migration error on deployment, follow these steps after you backup your deployment DB:

Along with bug fixes, ENV var support, Router enhancements, and improved TypeScript support, this release introduces a new workflow with CLI tools for contributing to the RedwoodJS Framework. For more information, please read CONTRIBUTING.md
🤩

This release includes Prisma-2.0.0-beta.2, which is a big update that has many improvements, bug fixes, and new features.
🚀
Prisma introduced a new relation syntax and support, which allows for complex relationships within `schema.prisma' models. RedwoodJS has improved its generators to support many model relations' use-cases. However, there are generator support limitations, which you can read about here on our community Forum.
👈

Additionally, Redwood now has a Netlify Plugin to set the DB provider during deployment. See the section below "Using the New Netlify Provider Plugin" for more information.

If that doesn't resolve the issue, then delete the contents of the deployed DB _Migration table (if applicable)

Using the New Netlify Provider Plugin (optional)

These steps only apply to Apps upgrading from previous versions. New Apps already include these changes.

Redwood apps running any version can use the Netlify Provider plugin, which eliminates workarounds required to use ’SQLite’ for local development and ‘PostgreSQL’ (or other DBs) for production deployment.

If you are using PostgreSQL in production, follow the steps below.

If you need to customize your DB provider (to use MySQL, for example), refer to documentation for 'netlify-plugin-prisma-provider’. Changing the provider is as simple as adding a new environment variable in Netlify.

Add the plugin package to your App

Redwood uses yarn workspaces. Run this command to add the package to the root package.json.yarn add -W netlify-plugin-prisma-provider

For example, if you completed the RedwoodJS Tutorial you would have posts.js and contacts.js within api/src/services/posts/ and api/src/services/contacts/, respectively. You would add the import statement to the top of each of those files.

(3 of 3) Update your @redwoodjs/* packages.

Four packages should be updated to v0.3.2

Root directory package.json

"@redwoodjs/core": "^0.3.2”

web/package.json

"@redwoodjs/web": "^0.3.2”

"@redwoodjs/router": "^0.3.2”

api/package.json

"@redwoodjs/api": "^0.3.2”

After updating and saving the files, install the packages from the root directory: $ yarn install

(2 of 3) Add the db import to each of your Services files

For each Services file within api/src/services/*, do the following:

add this line at the top:

import { db } from'src/lib/db'

For example, if you completed the RedwoodJS Tutorial you would have posts.js and contacts.js within api/src/services/posts/ and api/src/services/contacts/, respectively. You would add the import statement to the top of each of those files.

(3 of 3) Update your @redwoodjs/* packages.

Four packages should be updated to v0.3.0

Root directory package.json

"@redwoodjs/core": "^0.3.0”

web/package.json

"@redwoodjs/web": "^0.3.0”

"@redwoodjs/router": "^0.3.0”

api/package.json

"@redwoodjs/api": "^0.3.0”

After updating and saving the files, install the packages from the root directory: $ yarn install

In this release we continue towards making the steps in our tutorial a reality.

Added

A webpack plugin that automatically imports components from web/src/pages/* into Routes.js and an accompanying ESLint plugin that'll let you know when you're referencing a page that doesn't exist. #21@mojombo

getPaths into @redwoodjs/core that gives Redwood packages a single and stable place to references paths in a Redwood project. #24@peterp

This is the first release of hammer and it doesn't actually do anything useful
🎉

I've added the hammer-cli that allows anyone to add new commands in the the src/commands directory. Right now we only have a single generate command with a single component generator. The component generator plops a ⚒ hammer style component into the web/src/components folder of your hammer project.