Hi there, Encountering an issue when trying to run the webpack build:production task as per described here: https://github.com/roots/sage/tree/sage-9 Both the build and watch tasks work fine, but the build:production throws an error in emitpath.js. I believe it’s trying to supply an object instea…

have a look here [image] Whats the purpose of assetsPluginProcessOutput? sage Hi, EDIT: It’s working now. Here is the fix: https://github.com/roots/sage/issues/1659#issuecomment-223032889 Regards

Thanks! dani-z’s solution of changing path.extname() to path.format() in webpack.config.js worked.

Hi guys, I am experiencing the same issue with Sage 9 ; no solution so far. Any idea? Thanks.

We’re going to need a little more information than that. What have you tried?

Hi, Thanks for your answer. So I ran yarn run build:production and I got the following error: $ webpack --progress -p --config resources/assets/build/webpack.config.js error Command failed with exit code 2. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.````` …

Is this a vanilla copy of Sage, straight out of the box, or have you customized it at all before running yarn build:production ?

Well, I made some changes (added npm packages mainly). thanks.

I recommend removing the packages one by one and seeing which one causes it to break or un-break when added/removed. This will narrow down where the problem is. Once you know which package caused the issue, show us how you added the package and what changes you made to theme-name/resources/assets/sc…

Hi there, Thanks for that - I found the culprit. This is this plugin: http://idangero.us/swiper/#.Wbfge9OGNE4 I installed it from my package.json then, I basically import it at the top of my home.js using: import Swiper from "swiper"; And then in my finalize() function: new Swiper ('.swiper-c…

Error when running Sage build:production

sage

Nicolo_Sacchi July 2, 2016, 4:06am 2

have a look here