-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Official plugin registry #283
Comments
Like a package manager? What about using NPM? |
I think its overkill. The majority of the plugins are tiny post-process plugins. as Matthew says, you can search on npm and a PR to our docs isn't difficult. If we start getting 100's of plugins we can revisit. |
Agreed. The docs can get pull requests from people if others want to add to the list. If we get a longer list it can break off into its own section first, and then if the list gets too long too manage, decide then if we want to do something different. Having said that, I am interested in consuming a list of plugins in a data (JSON) format. @lukeapage are you tagging all plugins with "less plugins" as keywords in NPM? If so, maybe we could recommend that in docs, or some common way of tagging so it could be consumed with a search to: https://www.npmjs.com/browse/keyword/less%20plugins. Then it would be a kind of "unofficial-official" list in a package manager. |
I recently post some question here less/less-meta#5. Not the right place or not interesting. In summary i wonder how to distribute client side plugins? |
I noticed jQuery recently switched to NPM to host its plugins. An NPM blog post recommended to add |
+1 i will add the keywords from now |
To not increase the entropy of the universe I'll be using |
Do things according to specific rules help slow down entropy increment. |
Hi all,
Since Less now supports plugins, I think it would be sweet if we have an "official (recommended) plugin registry/list". (We kind of have one in current docs but I think we may need a mechanism of publish/register/submit plugins from the community.) It can prevent similar functionalities from being implemented several times and save developers lots of efforts when looking for suitable plugins.
The text was updated successfully, but these errors were encountered: