Change Details

As a user I want to use bridge on my underpowered devices so that I can contribute to free knowledge. Currently only the //init// build is happening with the target "application", while the //app// build is happening with the target //commonjs// (i.e. it is built as a library in order for ResourceLoader to be able to consume it, and the developers to be able to dispatch it at will). This results in less optimizations to be applied to it (//app//) than possible. **AC** * ResourceLoader can still load //app// and we can still dispatch it as module (i.e. not a script) * bundle size is decreased "as far as possible" * e.g. we continue to use the `http-status-codes` library, but only the constants we use of it are actually shipped to the clients **Notes** * it was suggested to "remove underused libraries", but we feel this is a last resort and instead we should actually try and achieve that we only ship the relevant parts but still leverage awesome 3rd party OSS

As a user I want to use bridge on my underpowered devices so that I can contribute to free knowledge. Currently only the //init// build is happening with the [[ https://cli.vuejs.org/guide/build-targets.html#library | target ]] "application", while the //app// build is happening with the target "commonjs" (i.e. it is built as a library in order for ResourceLoader to be able to consume it, and the developers to be able to dispatch it at will). This results in less optimizations to be applied to it (//app//) than possible. **AC** * ResourceLoader can still load //app// and we can still dispatch it as module (i.e. not a script) * bundle size is decreased "as far as possible" * e.g. we continue to use the `http-status-codes` library, but only the constants we use of it are actually shipped to the clients **Notes** * it was suggested to "remove underused libraries", but we feel this is a last resort and instead we should actually try and achieve that we only ship the relevant parts but still leverage awesome 3rd party OSS

As a user I want to use bridge on my underpowered devices so that I can contribute to free knowledge. Currently only the //init// build is happening with the [[ https://cli.vuejs.org/guide/build-targets.html#library | target ]] "application", while the //app// build is happening with the target //"commonjs// (i" (i.e. it is built as a library in order for ResourceLoader to be able to consume it, and the developers to be able to dispatch it at will). This results in less optimizations to be applied to it (//app//) than possible. **AC** * ResourceLoader can still load //app// and we can still dispatch it as module (i.e. not a script) * bundle size is decreased "as far as possible" * e.g. we continue to use the `http-status-codes` library, but only the constants we use of it are actually shipped to the clients **Notes** * it was suggested to "remove underused libraries", but we feel this is a last resort and instead we should actually try and achieve that we only ship the relevant parts but still leverage awesome 3rd party OSS