micro (dev) and micro-serve

[rauchg]

Right now micro has a convenient tool for preventing the setup of an entire Babel toolchain. Namely, you can run:

$ micro index.js

and index.js can use export, async, await and all the other goodies.

When going to production, this is unadvisable:

1. npm install takes longer
2. container images are larger
3. bootup time increases

For 3, the solution right now is clear: use micro index during development, use micro --no-babel build/index in production.

For 1 and 2, it'll be great to have micro be the convenience tool, and micro-serve or micro-prod be the tool for serving in production.

micro will additionally incorporate support for visualizing the requests in terms of the data flow, with built in JSON highlighting and prettifying, among other things.

Repository: https://github.com/zeithq/micro-serve

[rauchg]

Thanks @nkzawa for the feedback. micro will be dev-oriented. micro-serve will be the prod-only tiny tool that targets a build.

[leo]

Can be solved by merging https://github.com/zeit/micro-serve/pull/1 and #24.

[Floby]

If micro (dev) also had the babel toolchain setup and a command to build a project, that'd be even cooler =)

[leo]

@Floby I think we should rather build a Yeoman generator for that.

[Floby]

you mean one that sets up the build as a pre-publish hook ?

On 3 May 2016 at 16:01, Leo Lamprecht notifications@github.com wrote:

@Floby https://github.com/Floby I think we should rather build a Yeoman
http://yeoman.io generator for that.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#15 (comment)

[leo]

@Floby In the package.json of your project? Why not!

[Floby]

That'd be the safest place in order to have working published modules imo
Le 3 mai 2016 16:10, "Leo Lamprecht" notifications@github.com a écrit :

@Floby https://github.com/Floby In the package.json of your project?
Why not!

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#15 (comment)

[rauchg]

Update: all the runtime stuff now lives in micro-core. micro will remain a really quick way of testing and running your microservices, transpiling when necessary, and with beautiful CLI output (pending :D)

[leo]

Just opened a new issue for the visualisation part (separating the CLI from the core is finished): #33

[rauchg]

Moving this into #33. Thanks @leo