-
Notifications
You must be signed in to change notification settings - Fork 458
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
Micro is not very "lightweight" #234
Comments
|
Splitting what out? |
The development CLI... 😄 |
The code running is a lot less than express / koa, who cares about installed space in 2017? |
@albinekb Yea, that's my opinion. But sadly, a bigger package also means longer installation times in production (which makes deployments slow). |
@albinekb My assumption is that If you add If you add |
I'm getting 17mb now. @leo what's the status of splitting out the cli? |
@timneutkens thanks! what are you using to measure package size? the printout looks really nice! |
thanks! |
Very close! |
The split happened: |
I just checked v9.0.0 and it reports 747K. Great job! 🎉 Update 2018: You can visualize the install size difference between micro@7.3.3 and micro@8.0.0 with my new tool, Package Phobia, which is much easier than installing yourself 😄 |
In the readme it says "micro" and "lightweight", but doesn't say what the installed size is. So I went ahead and did my own tests.
mkdir micro-example cd micro-example npm init -y npm install --save micro du -sh node_modules
This shows 9.2M for
micro@7.3.2
and all it's dependencies.Now lets try with the popular express framework.
mkdir express-example cd express-example npm init -y npm install --save express du -sh node_modules
This shows 1.8M for
express@4.15.2
and all it's dependencies.I also repeated the same steps for
koa@2.2.0
(2M) andhapi@16.1.1
(1.3M) which are also popular web frameworks.That means micro is the largest of the frameworks one might use to make microservices.
Is this expected?
The text was updated successfully, but these errors were encountered: