Change require custom libraries to suggestions as a better method with more options

OPTION #2 is my preferred method

The jquery.fancytree library is in https://www.npmjs.com
Which allows us to get npm-asset/jquery.fancytree using the composer

Thank you so much for all the work you’ve put into helping out with this project @rajab natshah — it’s greatly appreciated! I understand this might be a preference issue, but I would love to keep my node packages managed by NPM and my PHP packages by composer.

Would it be possible to avoid making this a composer dependency or to make it optional? So a #3 option to the proposal?

For context, I manage my NPM packages in my project root and then copy the necessary files from node_modules to WEB_ROOT/libraries.

I see this nice option Joël . I agree to move our methods to your logic.

I see this Option #3 added to modules like CKEditor Anchor Link → or Ace Code Editor →

The method is doable.

I use the following in a theme

  "scripts": {
    "theme:init": "webpack --progress --config  webpack.config.init.js",

Which webpack.config.init.js copy only what we need to the target location

Something like Copy Drupal Libraries may work as a default in projects.

  "scripts": {
    "copy-drupal-libraries": "webpack --progress --config  webpack.config.copy-drupal-libraries.js",

const { merge } = require('webpack-merge');
const path = require("path");
const webpackConfig = require('./webpack.config');
const CopyPlugin = require("copy-webpack-plugin");

module.exports = merge(webpackConfig, {
  mode: 'development',
  devtool: false,
  plugins: [
    new CopyPlugin({
      patterns: [
        {
          from: path.resolve(__dirname, "node_modules/jquery.fancytree/*"),
          to: path.resolve(__dirname, "web/libraries/fancytree"),
          context: "node_modules/jquery.fancytree",
        }
      ],
    }),
  ],
});

Thanks @rajab natshah, I'm updating module to use both library and CDN as there were a lot of confusion.

Another method would be including the library with the module.
I also added successor library issue: ✨ Adding library with module, possible successor library Active

Seems like some updates broke the widget functionality.
Not working on both 10.3 and 11.0 😞
Investigating

@vladimiraus I found the patch at https://www.drupal.org/project/taxonomy_manager/issues/3474919 🐛 Form element taxonomy_manager_tree broken RTBC fixed the broken functionality.

The MR patch here (#3467549) combined with the MR patch there (#3474919) has it working via CDN in my tests.

To use the fancytree library locally, I find I still have to edit my project's main composer.json like so:

...
        "merge-plugin": {
            "include": [
                "docroot/modules/custom/*/composer.json",
                "docroot/modules/contrib/taxonomy_manager/composer.libraries.json"
            ],
        },
...

(note: I have wikimedia/composer-merge-plugin installed)

and then run composer require fancytree/fancytree -W to install it locally to /docroot/libraries. Is this the correct process?

Hello,

I was able to overcome all errors by using:

Method #2 define in post #6 ✨ Change require custom libraries to suggestions as a better method with more options Needs work
combined with this patch https://www.drupal.org/files/issues/2024-09-17/taxonomy_manager-3474919-... →
from: https://www.drupal.org/project/taxonomy_manager/issues/3474919 🐛 Form element taxonomy_manager_tree broken RTBC

Thanks!