Ben Irvin

Node engine in package.json is actually set to >=14.19.1. Does Strapi require that as a minimum? If so I'll check the point version as well.

On further review, I discovered that other versions of node (12 and 18) do actually work to generate a new project, but node 18 fails to install dependencies (and provides...

Running Strapi 3.5.4, I think I figured it out. I have the exact same error when using Postgres/bookshelf. Strapi runs completely fine normally with postgres. There aren't any missing modules....

Yarn.lock doesn't have any changes. The error seems to be that @strapi/data-transfer is missing, which is odd because I'm not getting that message locally and it is included in package.json...

@Convly I just checked. It works locally only because the `dist` folder exists. This is another hurdle to overcome with including typescript in the monorepo.

I will add a simple test of the `version` command to demonstrate how it can be used.

LGTM but one request: could you add a little test of something as proof it actually runs tests correctly? (Update: you've added some in the encryption PR so I'll try...

I just moved the logic for filename arguments into Commander where it belongs, now it's safer and cleaner to work with.

Considering that the way the user interacts with Strapi is the API and that's what most of these are testing, I'm not 100% convinced those couldn't still be considered e2e...

> I tthink it's wrong to consider CE tests as an incomplete version of EE tests. Those are 2 different versions and have tests in common but also specific tests...