Windows 10
Docker Desktop 2.1.0.1

Following instructions here:
https://mhy.js.org/basics/usage

Looks like some other permission is needed.

In the dashboard UI, when I scroll in a box, it makes the dashboard not responding, or too slow (like at least 10 seconds).

I am not mac os and I use iTerm2. I tested using Terminal also, it's the same.

When running /mhy config typescript, I get the following output:

{ compilerOptions:
   { module: 'esNext',
     target: 'esnext',
     moduleResolution: 'node',
     allowJs: false,
     emitDeclarationOnly: true,
     strict: true,
     jsx: 'preserve',
     resolveJsonModule: true,
     esModuleInterop: true,
     noImplicitAny: false,
     declaration: true,
     baseUrl: '/path/redacted',
     skipLibCheck: true,
     incremental: true,
     outDir: 'src',
     paths:
      { '*': [Array],
        '@': [Array],
        '@/*': [Array],
        '@/mhy': [Array],
        '@/mhy/*': [Array] },
     typeRoots:
      [ '/path/redacted/node_modules/mhy/node_modules/@types',
        '/path/redacted/node_modules/@types' ] },
  include:
   [ '/path/redacted/src/**/*' ],
  files:
   [ '/path/redacted/node_modules/mhy/dist/configs/typescript/mhy.d.ts' ] }

Notice how the paths contain [Array] only.

Not sure if this is by design, but IMHO there could be a depth flag similar to node's util.inspect(). For example --depth 0 or just no depth flag should print the full object (this would change the default behaviour of the command though).

WDYT?

I'm curioius for what purpuse your using mhy, how you use it and what is your overall experience with it?

Done (keeping them just because it looks cool)

• Refact the code to make it easier for other maintainers start on it easily
• Typescript support -> config
• Create documentation
• Official website
• Add command registering interface instead of implementing all commands in mhy
• Add CI for dist (along with sub-packages) + Docker image
• Update dependencies (being done continously)
• Remove postcss-cssnext in the favor of postcss-preset-env
• Rename @mhy/mhy to mhy
• Prettier refakt: detach from Babel, use Process
• Add Prettier to all available extensions it is supporting
• Add *Storm configuration docs
• Add VSCode configuration docs
• Make folders configurable (like src)
• Add mhy config, single source for stuffs like extensions, directories, etc.
• Implement a solution for correct array manipulation from package.json
• Add webpack-bundle-analyzer process
• Add tslint process
• Deprecate other mhy repositories and packages
• Appriciation option for contributors and dependency developers
• Add standalone storybook support
• Pass flags to WDS
• Make console functions allowed by eslint using development NODE_ENV
• Measure babel-loader cache options if compilation can be speed up
• Add jimp process (cancelled)

Next

• Create more examples
• More CLI ouput tests
• Create repository with test projects
• Add missing community profile pages
• Use svgr-loader instead of react-svg-loader (also investigate the removal of svgx extension)
• Add GraphQL toys (with GraphQL Codegen)
• Add backend toys for servers, API testing tools, OpenAPI mock server, etc.
• Add VueJS support
• Add Angluar support
• Introduce multiple sub folders instead of a single src (like ui, server, etc.)
• Rewrite whole codebase in TS
• Add svgo process
• Implement support for presets
• Add support for react-docgen-typescript-loader
• Add more verbose loggin
• Add more debug info
• Create unit tests
• Add out-of-the-box support for translations using Babel macros
• Add parcel support
• Add rollup support
• Add babel-plugin-redux-saga (only macro maybe?)
• Add support for locked mhy versions
• Optimize UI: speed
• Refact UI: Draggable, resizable, full mouse support
• Add https://github.com/pikapkg/web support
• Add https://github.com/okonet/lint-staged support
• Node 12 support for Docker image
• Setup a monorepo approach, use @mhy namespace again and refact codebase into smaller packages again.
• Add support for monorepo tools (eg. Lerna)
• Add support for dependecy presets (npm i mhy will still have everything together but there can be a choice to use @mhy/core only and install @mhy/preset-react separately for example.
• Auto update mhyDependencies?
• Run tests on deployments
• Add storybook-addon-react-live-edit
• Add support for command auto-complete (#20)
• Add new process for https://github.com/kefranabg/readme-md-generator
• Add new process for as-script
• Add new process for TypeDoc
• Add new process for serve
• Add process for https://github.com/urish/typewiz

Where is name and bin key?
What do you mean by rewrite?
What do you mean by link?

Are you using cmd on Windows? PowerShell? Other?

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 with npm install if we not specifying the special one

• when 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?

Hi,

Is it possible to add the support for propTypes from a TS React components (e.g. with https://github.com/strothj/react-docgen-typescript-loader)?

Thanks.