Closed (won't fix)
Project:
CKEditor Wordcount
Version:
2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Apr 2021 at 13:12 UTC
Updated:
29 Apr 2021 at 16:19 UTC
Jump to comment: Most recent
Comments
Comment #2
jcnventuraThe module should not define any composer dependencies on any library, other than the one specified in the optional composer.libraries.json file. The use of npm-asset requires the use of a composer plugin and some rules in the project's root composer.json file which would then need to be documented in the module README.md file.
Nothing prevents anyone from adding the library via npm-asset with versions 2.x of the module. On versions 1.x, this is not possible and the user must use the custom repository method explained in the module's page.
Comment #3
hchonovI am confused why is it okay for the module to require the use of the merge plugin but not okay to require using the installer plugin? The merge plugin adds a lot of overhead and runs twice over the dependencies.
Comment #4
jcnventura@hchonov is my colleague and we've talked about this.
Still, in case anyone stumbles upon this, the reason why it's not OK to require the asset packagist but is OK to suggest the use of the merge plugin is the fact that the last one is only a recommendation, not a requirement.
It is still possible to install the library via the use of a custom repository in the site's composer.json. Using
"npm-asset/ckeditor-wordcount-plugin": "^1.17"in the module's composer.json would force all module users to use the asset packagist and theoomphinc/composer-installers-extenderplugin to install the library.