Hello Seb, I'm -0 for this renaming due to 1) so far I don't think these modules might be useful to someone else 2) this is 2 minutes task so I would refactor just before publishing
Do you know someone who might need these modules? :))) OFF: maybe you know if it is possible to have "provided" NPM dependencies? :))) On Sun, 29 Aug 2021 at 12:23, seba.wag...@gmail.com <seba.wag...@gmail.com> wrote: > The current node modules are quite generic names. I think we should aim for > having unique names for those modules: > * They may otherwise clash with other already existing node modules > * We may want or have to publish some of those modules later (eg if we > introduce our own @lib-xyz module that provides some common functionality - > similar to a maven module) > > I may try contacting @bui...@apache.org <bui...@apache.org> to find out if > they have an idea about hosting for npm modules. Or if they recommend to > just publish to npmjs. > > Re renaming: All we need to do IMHO is to rename the "name" attribute in > the package.json file: > name="chat" -> name="apache-openmeetings-chat" > => and we can still use a different name attribute for the generated JS > file. Or alternatively change that name too. But it would not be required. > > Thanks > Seb > > Sebastian Wagner > Director Arrakeen Solutions, OM-Hosting.com > http://arrakeen-solutions.co.nz/ > https://om-hosting.com - Cloud & Server Hosting for HTML5 > Video-Conferencing OpenMeetings > < > https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url > > > < > https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url > > > -- Best regards, Maxim
