Brand new v5 install, error on first startup - Error: Cannot find module '@strapi\plugin-content-manager\package.json'

[jbeckton]

Bug report

Required System information

• Node.js version: v20.12.2
• NPM version: 10.5.0
• Strapi version: 5.0.0-beta.4
• Database: Postgres
• Operating system: Windows 11
• Is your project Javascript or Typescript: Typescript

When I run strapi report I get the following error.

Describe the bug

After generating my first strapi v5 app locally using the cli command npx create-strapi-app@beta strapi choosing the custom option as well as typescript and then providing my postgres db info. When I try and run the new strapi instance for the first time using npm run develop I get missing module errors. The modules that it is complaining about are plugins such as @strapi\plugin-content-manager.

Over the course of the last hour, I have tried to re-install and run strapi v5 a few times and have seen random missing module errors. These missing modules have all been from @strapi/plugin-*

Steps to reproduce the behavior

1. npx create-strapi-app@beta strapi
2. cd strapi
3. npm run develop
4. See error

Expected behavior

I would expect strapi to start up and allow me to finish setting up the local instance.

Screenshots

Here is the package.json file that the cli created.

In previous versions of strapi I did not have to add these core plugins via npm install.

[jbeckton]

To add some context to this issue. I created two instances of strapi locally using the steps described in the initial post. Niether would start up due to missing modules. I added the missing modules to the package.json file for both instances.

    "@strapi/plugin-content-manager": "5.0.0-beta.4",
    "@strapi/plugin-email": "5.0.0-beta.4",

The first instance will now start up and allow me to complete the installation. The second instance will not. The difference in the two instances is that the one that will not run is located inside a mono-repo manage by Turborepo.

There are possibly two issues here. One is that the cli did not set up the package.json correctly for both instances, hence the missing packages.

The second issue is that even after adding the missing packages for the second instance (mono-repo) the loaders do not have the correct path when search to load these modules.

I can run strapi v4 inside a mono-repo as many times as I want but with v5 it does not seem to work. I am unable to load the strapi instance for the first time to complete the set up in the second instance (mono-repo).

[derrickmehaffy]

Can't reproduce in beta.5