lakhman
commented
8 years ago I can reproduce this issue with a fresh new symfony install.
(You can copy and paste this into your terminal in one go to get up and running with the same error).
PROJECT_NAME=webpack-adminlte && echo $PROJECT_NAME
WORKING_DIR=~/Sites && echo $WORKING_DIR
cd $WORKING_DIR
# Create a new symfony 3 project && enter it
symfony new $PROJECT_NAME && cd $PROJECT_NAME
# Install webpack-bundle
composer require maba/webpack-bundle
# Update AppKernel.php
cat <<'-EOF' > app/AppKernel.patch
--- a/app/AppKernel.php
+++ b/app/AppKernel.php
@@ -15,6 +15,7 @@ class AppKernel extends Kernel
new Symfony\Bundle\SwiftmailerBundle\SwiftmailerBundle(),
new Doctrine\Bundle\DoctrineBundle\DoctrineBundle(),
new Sensio\Bundle\FrameworkExtraBundle\SensioFrameworkExtraBundle(),
+ new Maba\Bundle\WebpackBundle\MabaWebpackBundle(),
new AppBundle\AppBundle(),
];
-EOF
# Patch the AppKernel with our new bundle
patch -p1 -l < app/AppKernel.patch && rm app/AppKernel.patch
# Setup maba
yes | console maba:webpack:setup
# Make our entry file
mkdir -p app/Resources/assets && touch app/Resources/assets/main.js
# Compile the assets for the first time
console maba:webpack:compile --env=prod
# Fails here with the above error
# Why?
mariusbalcytis
I've got this working in development, but when I run the compile command for production, I get the following error:
Main error:
Full output:
Any ideas why it's trying to load the collector when compiling for production? I've checked my configuration against the demo bundle of this project (which runs as expected). I can't seem to find any obvious differences. (Configuration is exactly the same - the default symfony config).