Download to read offline
Uploaded byYosuke Torii
Module Management for ES6 Generation
The document discusses module management for ES6 generation. It recommends resolving version conflicts to keep dependencies flat and reduce resource size, allowing module optimization by users without compression by providers. It also suggests indicating private packages to prevent invalid accesses. Modules should not depend on specific ecosystems and loaders should work across ecosystems.
Module Management for ES6 Generation
- 1. Module Management forES6 Generation
- 2. - Resolve versionconflict and keep them flat to reduce resouce size(using Semver guideline). - No compression by module provider for optimization by user side. - Some way to indicate package private to prohibit invalide accesses can be better.
- 3. foo bower_components private main common 0.9 util unused common 0.8 bar foo bar sub app ui compatible all(deduped) private main sub foo util bar ui app all private main sub foo util private main bar ui app
- 4. - Modules neverdepend on specific ecosystem. - Loader will be work over defferent ecosystems.
- 5. foo bower_components private main common 0.9 util unused sub foo import common from '../common/dist/main.js' import common from 'common' base = ./bower_components 'common' => ${base}/common/dist/main.js Module Loader static dynamic
- 6.
- 7.