Delivery of a new project on Nov. 15th. Should I stick to v4 or run the v5?

Discord Q&A strapi-questions
1

I know the answer to this question is not easy.

I’ve started developing a new project a few days ago and jumped on the v5. As any first release of a major version, I was expecting some issues and that’s fine. There are a few issues that will already be fixed in 5.0.1.

Based on your own review of the issues, do you expect v5 to be in a production-ready state by Nov 15th?

Should I reboot the project on v4 for now and upgrade later?

Thank you for yopur guidance. And great work! I love the new v5!

This topic has been created from a Discord post (1288535342500151297) to give it more visibility.
It will be on Read-Only mode here.
Join the conversation on Discord

2

The fact that the REST API has changed as well as the document system would imply some work on the frontend site to migrate from one to the other :confused:

3

IDK but the GraphQL-plugin drop support upload mutation, that mean the Upload scalar is dropped from the types
I’m trying add it manually but no luck for 6hrs :weary:

If you new project have some upload feature and using Graphql-plugin, this will adding some point to stick to v4 instead of the <a:v5pet:1149027072124145774>

Btw that if anyone successfully migrate the Upload Scalar to the v5, help is veryyyyyyy welcome…

4

Okay, managed to add the Upload Scalar

// upload.ts
import { Upload } from “graphql-upload-ts”;
import { ASTNode, GraphQLError } from “graphql”;

export const UploadScalar = ({ nexus }) => {
return nexus.scalarType({
name: “Upload”,
description: “The Upload scalar type represents a file upload.”,
parseValue(value: { promise: Promise }) {
if (value instanceof Upload) return value.promise;
throw new GraphQLError(“Upload value invalid.”);
},
parseLiteral(node: ASTNode | ASTNode) {
throw new GraphQLError(“Upload literal unsupported.”, { nodes: node });
},
serialize() {
throw new GraphQLError(“Upload serialization unsupported.”);
},
});
};

5

Thanks. Fortunately mine a pretty standard one :wink:

6

FYI the reason we dropped the upload option from graphql is the literally only package we could use to support it (graphql-upload) decided to go ESM only and no longer support CJS (he was quite rude to us about it) so we had no other choice