ERROR After upgrade

[dthyresson]

@khatyan Upgrading from 0.15 to 0.32 is a sizeable chamge!

As @thedavid notes in the announcements and release notes for each:

Redwood v0.32

v0.32.2 Highlights <Set> now takes the prop private to mark a set of routes as Private For those who like to be less verbose, you can now mark a whole set of Routes as private, without wrapping it in an explicit <Private>block. All the juicy details here: Redwood Router docs Secure Services are available (experimental) Auth is hard. So is accidentally exposing functionality to the interwebs because you forgot to check for auth in your graphQL qu…

Upgrading to a version that is not the latest?

The command yarn rw upgrade will always upgrade to the latest (i.e. most recent) Redwood version. If you need to upgrade incrementally to a earlier, specific release, use the --tag option. For example, if you need to upgrade from v0.27.0 to v0.28.4, run the following command:

yarn redwood upgrade --tag 0.28.4

You’d want to do some incremental upgrades and follow each of the release notes and changes.

There are some significant config and path changes regarding db/Prisma and others in the 0.25 range.

If your v0.15 app is still small, I’dd suggest creating a new app with 0.32 and reworking the schema to match the latest. I think that would be much much easier than upgrading from such an early “alpha” release.