-
Notifications
You must be signed in to change notification settings - Fork 32
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
How can we improve mhy? #15
Comments
Thanks for the suggestions. There are definitely several areas for improvements. For the dependency issues I already have similar solution in mind in the form of presets and keeping mhy to be a thin client but it needs a lot of changes. One of mhy's mission is making the tools work well together using the latest versions. Installing the latest versions automatically won't guarantee that the tools will work together. For example ESLint 6 is out but they have some radical changes which broke how several other projects and mhy was using it. Having the latest installed automatically would break all tools in mhy. mhy is basically running the command's of the respective tool. For example when you run Btw for dependency management I've added some tooling that will help you manage dependencies coming from mhy, but it's not finished yet. |
We can have a config for specific projects like airbnb or whatever, with json of packages which you need for this project and if it's needed the version can be specified in this config. It should solve issues like eslint has now. |
And yes, it should be tiny with dependencies, that's the main concern which everyone has i guess using it, because everyone has it's own lovely set of packages, so if you have a good idea how can we implement this i would be love to help. |
I'm thinking about using mhy for myself, but i don't like few things:
the list of dependencies is huge, and beside babel, ts, webpack and react i don't need others (so i would love to have something like search with autocomplete here) or some presets with checkboxes, i see what https://www.npmjs.com/package/inquirer has good menu constructors with autocomplete.
i don't think what it's a good idea to update
packages.json
all the time when the new version of some package is updated, i guess it should just fetch the latest versions withnpm install
if we not specifying the special onewhen the port is busy i recommend to search for free one with something like this https://www.npmjs.com/package/get-port
@wintercounter what do you think about this?
The text was updated successfully, but these errors were encountered: