Component registration updated

[vikas-cldcvr]

Checklist for raising a PR

• Gone through UX documnetation for adding new features.
• All necessary unit tests covered.
• Required comments added for generating component manifest file? you can find details here
• Did you check the contributing doc?
• Did you check the existing issues for similar queries?

Describe your PR

@ollion/flow-core

[3.0.0] - 2024-04-29

Major/Breaking Changes

• Auto web component registration was removed to facilitate tree shaking.
• To register component manually please check here

@ollion/flow-code-editor

[2.0.0] - 2024-04-20

Major/Breaking Changes

• Auto web component registration was removed to facilitate tree shaking.
• To register component manually please check here

@ollion/flow-form-builder

[3.0.0] - 2024-04-29

Major/Breaking Changes

• Auto web component registration was removed to facilitate tree shaking.
• To register component manually please check here

@ollion/flow-lineage

[4.0.0] - 2024-04-29

Major/Breaking Changes

• Auto web component registration was removed to facilitate tree shaking.
• To register component manually please check here

@ollion/flow-log

[3.0.0] - 2024-04-29

Major/Breaking Changes

• Auto web component registration was removed to facilitate tree shaking.
• To register component manually please check here

@ollion/flow-md-editor

[3.0.0] - 2024-04-29

Major/Breaking Changes

• Auto web component registration was removed to facilitate tree shaking.
• To register component manually please check here

@ollion/flow-table

[3.0.0] - 2024-04-29

Major/Breaking Changes

• Auto web component registration was removed to facilitate tree shaking.
• To register component manually please check here

[sonarqubecloud]

Quality Gate passed

Issues
8 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[NikhilVerma]

I think barrel files are not handled when doing tree shaking https://vitejs.dev/guide/performance#avoid-barrel-files

We should try enabling sideEffects option in package.json and check if Vite can tree shake unused components - https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free

[NikhilVerma]

We can try publishing a beta version, and check if vite handles this correctly