Hello, Sorry but I disagree with all of you.
Please take a look at https://github.com/Jermolene/TiddlyWiki5/issues/2817 to se my motivations. I think the best place to put tiddlywiki plugins is npm. Just think about it, how do you install tiddlywiki on node? from npm, them, where will probably be your next stop to look for plugins? Probably npm too. Also it will have a positive impact if you just search for tiddlywiki on npm and see the package and a large list of plugins available, that are just one `npm install pluginname` away. So this will also give greater visibility to the project Lots of projects use this approach: yeoman generators, react plugins, angular directives, babel plugins, gulp plugins, webpack plugins... it is even used for non Javascript code: typescript definitions, cordova plugins I'm not sure why, but on tiddlywiki community there is a is a trend towards re-inventing the wheel, creating everything from the ground up. I don't see the problem on using battle tested industry wide accepted solutions. And having tiddlywiki plugins on a fantastic highly scalable delivery mechanism like npm is something good. Obviously this is not for the users that access tiddlywiki from tiddlywiki.com, but for all people that uses the node-js version this will be the desired way. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/9b193ea1-4039-46ea-a843-da501423cba8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
