npm installed autobahn-js size is 120M
See original GitHub issuehaving just autobahn-js v19.6.2 installed,
120M ./node_modules
it’s much improved compared to v19.4.1 which was 281M. but as we are developing IoT device with small data pool allowed, we can’t afford this big library. is there anything I can do to reduce the module size?
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
autobahn - npm
Start using autobahn in your project by running `npm i autobahn`. There are 115 other projects in the npm registry using autobahn.
Read more >autobahn-js/building.md at master - GitHub
The following describes how to build and publish Autobahn|JS for browser and Node. Build environment (browser build). Install Node.js. sudo apt-get ...
Read more >giT - River Thames Conditions - Environment Agency - GOV.UK
Filezilla 3 beta, Dereon shoes size 12, Pudin de vainilla, Parques disneylandia ... 311 jupiter lyrics, Free line stickers canada, Reichsautobahn breslau, ...
Read more >Untitled
Jorge chizzini, Hale ohuna noodle, Twitter obama putin, Kia autobahn, ... Ich habs gemerkt englisch, Infant polo boots size 1, Lalbenque france!
Read more >Untitled
Chanupa venta, Lingua veneta nonciclopedia, Jw davis da-120 m, Mid range family ... Us escaudain, 3 short beeps on boot, 61803 bearing size,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So I looked into this a bit and found that https://github.com/ethereum/web3.js handles a similar situation cleanly. They put every package into a
packages
directory where they have their ownpackage.json
file. The root of the source tree also has apackage.json
which is only for the ethereum core.If we replicate a similar model we will have root ==> packages ==> autobahn/lib/ root ==> packages ==> autobahn-xbr/lib/
Then the autobahn-xbr library could also add a
PeerDependencies
entry for autobahn but more importantly I want to mention that the xbr library has no direct dependency on autobahn, the library only expects aSession
instance created by a user’s app.fixed via https://github.com/crossbario/autobahn-js/pull/453