-
Notifications
You must be signed in to change notification settings - Fork 365
Package size #342
Comments
@remicastaing very interesting. Would be great if you could test it out. I have not spent time to optimize the package sizing yet but I am sure there is scope for optimization. |
I just deployed the minified service and it seems to work: playground and graphiql are responding and I'm getting a During packaging, I'm getting two warnings:
|
If I'm trying to use |
Right now we are not using merge schemas but would use it in future. Maybe we can keep this issue open till we have an answer. |
If, like me, you encounter some issue by packaging some npm module, just use (I dropped |
Hello every one! Thanks for the awesome work.
I'm looking at the package size after running
sls package
:If you look into the .zip files you will find all the node_modules, with readme, test, src, etc. Is not there any way to get rid of all this dead weight?
If you remove:
from
webpack.config.js
, you can go down to:And if you add
uglifyjs-webpack-plugin
, you can shrink the package to:Disclaimer: I have not tested if the service is working after deployment.
The text was updated successfully, but these errors were encountered: