npm run setup doesn't work in 3.0.0-alpha.12

[abdonrd]

Node.js version: v9.8.0
npm version: 5.8.0
Strapi version: 3.0.0-alpha.11.2
Operating system: macOS

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce the problem

strapi new strapi-demo
cd strapi-demo
npm run setup

What is the expected behavior?

The setup working.

[lauriejim]

I think if we close this issue #778 it will fix your issue.
object spread is the problem :/

[abdonrd]

@lauriejim but I have had this issue using Node v9.8.0.

[abdonrd]

Only as suggestion, I propose to move it to v3.0.0-alpha.11.3, because it starts to fail in v3.0.0-alpha.11.2. With v3.0.0-alpha.11.1 works well.

[abdonrd]

Maybe the bug is from #773, since it is the moment in which file strapi-plugin-users-permissions/services/UsersPermissions.js was edited.

[bugvish]

Quick and dirty hack:

Change Line 140 of /strapi/packages/strapi-helper-plugin/node_modules/babel-core/lib/transformation/file/index.js to:
plugins: ["jsx","flow","objectRestSpread"]

[L8NiteOwl]

Thanks, @bugvish! I was really scratching my head on this one. This temporary hack worked perfectly for me.

[abdonrd]

I just tried with the new version (v3.0.0-alpha.12) and it still happens.

[soupette]

@abdonrd I currently working on this command, and I'm facing the same issue as you do...

I'm facing two problems here:

• Webpack is trying to build folders that are not included in its configuration (entries)
• The babel-loader does not seem to use the babel-plugin-transform-object-rest-spread plugin.

Currently I'm trying to find out why webpack is building the services folder when we try to build only the admin and why we manage to build the plugins from the monorepo whereas it doesn't work inside a project 🙈🙈🙈.

[soupette]

#1033