Issue #3349271: The use of the module sould not be mandatory in production

The idea is to allow switching to another "module mode" with a new configuration flag in the settings

In this mode, It would be ok to keep standard Drupal library configuration in production and allow users to use the module as a development dependency.

It assumes the following inconvenients :

• The manifest has been generated at least once in order to use the dev mode
• All dependencies have to be explicitly declared in vite.config as they are in libraries.yml (and so hashes can't be used in file names in vite config)

This code should not break the current and default use of the module

marked this merge request as draft

restored source branch 3349271-the-use-of

marked this merge request as ready

changed the description

marked this merge request as draft

added 2 commits

• 1e93605c - noissue: Access level to 'AssetLibrary::' must be 'protected' (as in class...
• f002d50c - noissue: remove dumps

Compare with previous version

marked this merge request as ready

marked this merge request as draft

added 5 commits

• d0e17331 - 1 commit from branch project:1.x
• 4cac35f3 - Fix phpcs
• 3ed32703 - vite-3349271: fix phpstan
• 059b6819 - Merge branch '1.x' of git.drupal.org:project/vite into 3349271-the-use-of
• 838fbf18 - 3349271-the-use-of: add admin config form for the module to enable a new building tool mode

Compare with previous version

added 1 commit

• f1f61f32 - 3349271-the-use-of: add new config flag 'advancedMode' in settings to allow an...

Compare with previous version

added 1 commit

• beda2a82 - 3349271-the-use-of: clean config residues because of deletion of the adminForm...

Compare with previous version

marked this merge request as ready

changed the description

added 1 commit

• ae9e3c10 - Clear orphan vite.permissions.yml initially created to add an admin page for the module

Compare with previous version

https://www.drupal.org/project/vite/issues/3349271#comment-15147413

closed