#Remove drupal console how to#
#Remove drupal console update#
#Remove drupal console code#

drupal/console-extend-plugin is locked to version 0.9.4 and an update of this package was not requested.

drupal-composer/drupal-scaffold 2.6.1 requires composer-plugin-api ^1.0.0 -> found composer-plugin-api but it does not match the constraint.

drupal-composer/drupal-scaffold is locked to version 2.6.1 and an update of this package was not requested.

cweagans/composer-patches 1.6.6 requires composer-plugin-api ^1.0 -> found composer-plugin-api but it does not match the constraint. cweagans/composer-patches is locked to version 1.6.6 and an update of this package was not requested. composer/installers v1.6.0 requires composer-plugin-api ^1.0 -> found composer-plugin-api but it does not match the constraint. composer/installers is locked to version v1.6.0 and an update of this package was not requested. Your lock file does not contain a compatible set of packages. You may need to run composer update with the '-no-plugins' option. The 'drupal-composer/drupal-scaffold' plugin was skipped because it requires a Plugin API version ('^1.0.0') that does not match your Composer installation ('2.1.0'). The 'drupal/console-extend-plugin' plugin was skipped because it requires a Plugin API version ('^1.0') that does not match your Composer installation ('2.1.0'). The 'cweagans/composer-patches' plugin was skipped because it requires a Plugin API version ('^1.0') that does not match your Composer installation ('2.1.0'). The 'composer/installers' plugin was skipped because it requires a Plugin API version ('^1.0') that does not match your Composer installation ('2.1.0'). On running any Composer command the following is outputted: drupal-composer/drupal-scaffold plugins.Composer will not work in these environments. The Drupal 8 sites now have Composer and Drupal Composer plugins that are expecting to use Composer 1 API. I have other Drupal 8 sites running on the same server. As part of that process we looked at upgrading Composer 1 to 2. In a previous article we looked at upgrading 8.9.19 to 9.2.6. # WordPressĬonsider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page.The Topic: Upgrading Drupal 8.9.20 to 9.3.0 - resolving globally installed Composer 1 and 2 issues. If you are not server-side rendering and using the Vue router, split the bundles by lazy loading routes. Otherwise, code-split using a third-party library such as loadable-components. If you are not server-side rendering, split your JavaScript bundles with React.lazy(). # Magentoĭisable Magento's built-in JavaScript bundling. # JoomlaĬonsider reducing, or switching, the number of Joomla extensions loading unused JavaScript in your page. # DrupalĬonsider removing unused JavaScript assets and only attach the needed Drupal libraries to the relevant page or component in a page. If you are using Angular CLI, include source maps in your production build to inspect your bundles. # Build tool for support for removing unused codeĬheck out the following Tooling.Report tests to find out if your bundler supports features that make it easier to avoid or remove unused code:

#Remove drupal console code#

The Coverage class in Puppeteer can help you automate the process of detecting unused code and extracting used code. The Coverage tab in Chrome DevTools can give you a line-by-line breakdown of unused code.

#Remove drupal console how to#

# How to remove unused JavaScript # Detect unused JavaScript See the Lighthouse performance scoring post to learn how your page's overall performance score is calculated.