paulbratslavsky/demomigration

Strapi API

Available Scripts

In the project directory, you can run:

yarn

yarn installs all dependencies to make this project work.

yarn seed

yarn seed seeds demo data.

You need to run this command before starting your project

yarn develop

yarn develop starts the server in developement environment and builds the administration panel. Open http://localhost:1337/admin to view it in the browser.

demomigration's Issues

`yarn seed` outputs "Failed to move C:\test\demoMigration\data\uploads to public\uploads"

Running Windows 10 64-bit, with node v14.18.2 and yarn v1.22.19

To reproduce:

• git clone https://github.com/PaulBratslavsky/demoMigration.git
• In the new folder, run yarn.
• After that's completed, run yarn seed.

For me, this gives the error "Failed to move C:\test\demoMigration\data\uploads to public\uploads".

I'm not sure what else to do here, but I do notice that the "demoMigration\data\uploads" folder/file is never created, which is probably why it can't be moved to the "public\uploads" folder. I hope this helps!

Upgrading Project to v3.6.11 breaks Admin Panel

Hi,

This project currently runs on Strapi v3.5.0. I wanted to upgrade the app to v3.6.11, to maximize compatibility when migrating the whole thing over to v4.x.x. However, upgrading this project to v.3.6.11 seems to break the admin panel, with the following error:

Uncaught TypeError: Cannot read properties of undefined (reading 'add')
    at main.24944e7c.chunk.js:1:9637145
    at Array.forEach (<anonymous>)
    at t.default (main.24944e7c.chunk.js:1:9637110)
    at main.24944e7c.chunk.js:1:1900074
    at Array.forEach (<anonymous>)
    at Object.<anonymous> (main.24944e7c.chunk.js:1:1900031)
    at a (runtime~main.6063a9f5.js:1:561)
    at t (runtime~main.6063a9f5.js:1:430)
    at Array.r [as push] (runtime~main.6063a9f5.js:1:293)
    at main.24944e7c.chunk.js:1:47

As upgrading from 3.5.0 to v3.6.11 is not supposed to include any breaking changes, I would expect to update the project and rebuild with no issues.

To Reproduce:

• Modify package.json dependencies to the following (Changing to 3.6.11 and adding "strapi-plugin-i18n"):

"dependencies": {
    "body-scroll-lock": "^3.1.5",
    "fs-extra": "8.1.0",
    "knex": "0.21.18",
    "lodash": "^4.17.5",
    "reactour": "^1.18.0",
    "sharp": "^0.30.7",
    "sqlite3": "^5.0.11",
    "strapi": "3.6.11",
    "strapi-admin": "3.6.11",
    "strapi-connector-bookshelf": "3.6.11",
    "strapi-plugin-content-manager": "3.6.11",
    "strapi-plugin-content-type-builder": "3.6.11",
    "strapi-plugin-email": "3.6.11",
    "strapi-plugin-graphql": "3.6.11",
    "strapi-plugin-upload": "3.6.11",
    "strapi-plugin-users-permissions": "3.6.11",
    "strapi-plugin-i18n": "3.6.11",
    "strapi-utils": "3.6.11",
    "unzip-stream": "^0.3.0"
  },

• Delete node_modules, .tmp (issue happens regardless of existing/new/seeded/unseeded db), package-lock.json, build.
• Run npm install
• Run npm run build
• Run npm run develop
• Open localhost:1337/admin in your browser, and open the devtools console. You should see the error.

To ensure the issue likely lies somewhere in the project, I started a brand new boilerplate v3.6.11 Strapi app. I npm install'd, built, ran and confirmed that it would properly launch.

I then deleted the api, config, extensions folders, and pasted in the admin, api, components, config, exports, extensions and middlewares folders from this project. Cleaned, rebuilt, relaunched; gives me the exact same error.

Any help or advice would be much appreciated! I'm just trying to get this test project properly upgraded to V4 before we try it on our client's real application 😅