core-bundle | Contao Core Bundle | Web Framework library

Your advice worked msg. I installed the recipes with composer recipes:install symfony/webpack-encore-bundle --force -v and now yarn encore dev compiles webpack successfully. I now also know that I accidentally kept the package.json from the video in my project which explains why my error changed from Command encore not found to Error: Encore.enableStimulusBridge is not a recognized property or method. webpack.config.js:26 Object.

Considering your output:

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

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

You should not write your -tag yourself and instead use the commented encore_entry_link_tags instead. The encore_entry_link_tags will make sure it points to the file generated by Webpack Encore (after calling yarn encore dev for example).

When you use Webpack Encore use the webpack.config.yaml to point to your CSS in assets using addEntry('app', ...file..) (or possibly addStyleEntry, but addEntry should be fine). Webpack Encore takes the file under assets/styles/app.css and then puts it in public/ by default public/build. Depending on your configuration it might be, that your file name will not stay the same during that process. The good thing is Webpack Encore usually takes care of everything for you. (If not feel free to open a question for that).

See also: https://symfony.com/doc/current/frontend/encore/simple-example.html

You should use forward slashes, e.g. assets/styles/app.css. If you don't use Webpack Encore then you should make sure that you have the file in public/assets/styles/app.css to make it accessible for your browser. You should also wrap this into another helper function called asset. In other words it should look something like (assuming the path is correct):

The problem is not really in monolog-bundle but as follows:

• monolog-bundle requires symfony/http-kernel ~3.4 || ~4.0 || ^5.0
• You restricted all Symfony components to 5.0 (by setting "extra" -> "symfony" -> "require" to 5.0.*). So the only fulfillable requirement for monolog-bundle is http-kernel 5.0.*
• roave/security-advisories works by purposely conflicting with lib versions that have known security issues. In this case, every 5.0.* release has vulnerability CVE-2020-15094 (see https://symfony.com/blog/cve-2020-15094-prevent-rce-when-calling-untrusted-remote-with-cachinghttpclient) and is therefore blocked. So there is no valid version left and Composer aborts.

My suggestion: Symfony 5.0 reached end of life, so use the current release Symfony 5.2.x (Composer constraint "^5.2"). As Symfony uses strict Semantic Versioning there is no disadvantage for going to 5.2 instead of 5.0 (i.e. all code that runs on 5.0 will also run on 5.2).

You need to remove it also from the composer.json "auto-scripts" section, you probably have something like this:

You'll need to install all extensions needed manually. In your case, you are missing the XSL extension. This should at least fix the XSL issue.

I fixed it by adding const $ = require('jquery'); global.$ = global.jQuery = $; in the assets/app.js file.

Ocramius is well known for his harsh stance in maintaining backward compatibility.

On this case, release 2.9.0 says:

This release upgrades ocramius/proxy-manager to use composer-runtime-api:^2: this means that you will need composer:^2 to install this version of ProxyManager.

In order to upgrade to composer v2, you can run composer self-update --2 on your development or CI/CD system.

So your options are:

• either upgrade composer to version 2 (composer self-update --2), which is really the recommended way to go unless you have some specific composer plugin that you really need and hasn't been updated to account for the new release.

• Find which package you are installing is the one that requires the proxy-manager (composer why ocramius/proxy-manager), and see if you can adjust your version constraints on that package so that it depends on an older (< 2.9) version of ocramius/proxy-manager. (I mention this option only for completeness sake, but upgrading composer is really the way to go).

This bundle does not support Symfony 4 and 5.Use the Maker bundle instead.

maker bundle :

https://symfony.com/doc/current/bundles/SymfonyMakerBundle/index.html