Open rauchg opened 5 years ago
I would love to see more supervision for Hyper store. The goal is that developers have a nice place to upload their creations. It would be a good idea to encourage the community to create plugins, improving the documentation : )
My Hyper "wishlist":
I get what I'm asking for here is all really what you'd find working in an actual company environment, not so much an open source project. But hey, you asked. I love this project and hope to see it grow into what it should be. Cheers.
(Edit) More things to the wishlist:
hyper i <plugin>
or added to the plugin
array in ~/.hyper.js
kills overall performance. My work around so far has been to install plugins/themes to localPlugins
then refactor multiple plugin functionality into a single localPlugin
. It's the duplication of dependencies in node_modules
that really weighs things down.$HOME
directory. Maybe have it to where if the developer wants to use their hyper.js
config file, then have the development environment accept an alternative path to read that file from. hyper i <plugin> --local)
package.json
of then plugin/theme using validation logic inherit to Hyper. (i.e. in package.json
have a hyper
key which accepts an object as its value. Within the object, have a key type
with the value as a string Hyper parses as plugin
or theme
. Then while using Hyper, the user can enable/disable plugins and themes using the OS's menu options.)(Edit again...) The more I think about it, why even have the distinction between localPlugins
and plugins
. Other than say for development purposes, why not just install all plugins to the user's hyper_plugins
folder on their machine?
Is Zeit hiring? Clearly I need to just come on board and take care of implementing features lol.
Thanks!
I have been using Hyper for a while but only recently started keeping an eye on the issues page, just to see if there was anything I could help with. However, it sees like there are a lot of Pull Requests, and Issues that are made but they just sit there -- ignored. Its not that any of the Pull Requests seem to have any issues that are yet to be resolved, or any comments etc.
Some more proactive handling of Pull Requests, as well as Issues could really help. However, at the end of the day, this is also a Open-Source project, and I am happy to contribute in any way that may be helpful, whether that's helping with issues, pull-requests etc, or contributing code.
This is sort of an umbrella issue to discuss:
I'd love the input from the community to know what you'd like to see in terms of this goal.