symfony-bundle | Let 's Encrypt/ACME bundle for Symfony | Encryption library

The package you are using is not compatible with doctrine/dbal >= 3.

You can this to your composer.json and reinstall, so that your project uses DBAL 2:

Since you are not installing the "bundle" using composer, the autoloader does not get generated, and the class pertaining to your new package will never be found.

The bundle's composer.json file is irrelevant, since again, you are not installing the package through composer. Thus, it's never read.

But you can instruct composer to generate autoloader files that take this new bundle into account.

Let's say that this is your directory structure:

It seems that export command isn't environment-proof.

Finally, I removed these lines:

Considering your output:

Restricting packages listed in "symfony/symfony" to "5.0.*"

You currently have something like this in your composer.json:

The short answer is, that your bundle should contain a Resources/public/ folder with the built production assets in it. You can use the assets:install-command to copy or symlink these files into your project's public/ directory where it will automatically be placed in a subdirectory named after your bundle, so for example public/bundles/appbundle/. In your bundle you can then assume this path exists and load assets from there, e.g. in a twig-template with the asset-helper: {{ asset('bundles/appbundle/images/my_image.jpg') }}.

If you want to use EasyAdminBundle as a reference, here is an explanation how it works there:

Yes, EasyAdminBundle provides a webpack.config.js, but it is mainly for development and will never be used by your application. Instead the configuration will write the production assets to the appropriate places inside the bundle (namely src/Resources/public):

Since the translator doesn't read the request locale as said by @yivi, and I do not want to give the request locale to all my call to trans. I added a Listener that listen all KernelEvents::REQUEST and set locale into Translator: