Enable treeshaking

[s-yadav]

Proposal

Right now we add all the methods in default export so that we can access the method directly from Brahmos namespace. like
Brahmos.Component, Brahmos.createElement etc.

This was done so the aliasing of React to Brahmos can be done easily. But it necessarily increases the bundle size.

Though this might be required on umd bundle, but for es modules, we are not able to utilize proper tree shaking.

Plus this issue can be solved on compiler level easily on below code,

import Brahmos from 'brahmos';

class App extends Brahmos.Component {
    render Brahmos.createElement('div', {}, 'Hello World!')
}

we can easily find Brahmos.Component usage and can optimize the above syntax to

import {createElement, Component} from 'brahmos';

class App extends Component {
    render createElement('div', {}, 'Hello World!')
}

Complexity

• How this can work with third-party react components. The babel plugin does not run on node modules.
• Handle mangling done by the optimizers (Uglify, Terser etc)