.png)
Difference Between LWC & AURA
- Bundle Structure: LWC requires manual creation of a folder to host all your component files. Component HTML, JS, Configuration files are mandatory. CSS and SVG are optional.
- Naming Convention: The only noted difference in naming is while you’re referring component in another component. The new syntax uses kebab-case, instead of the camelCase
- Events: Unlike component or application events in Lightning Component, LWC used Standard DOM events.
- Lightning Locker: Lightning Locker is enabled by default in all custom LWC.
LWC Supported Features / Elements
Supported Features
- Lightning Experience
- Salesforce App
- Lightning Communities
- Lightning App Builder
- Community Builder
- Standalone Apps
- Lightning Components for Visualforce
- Lightning Out (Beta)
- Custom Tabs
- Utility Bars
- Flows
- First – Generation Managed Packages
- Second – Generation Managed Packages
- Unlocked Packages
- Unmanaged Packages
- Change Sets
- Metadata API – Lightning Component Bundle
- Tooling API – Lightning Component Bundle, Lightning Component Resource
- EMP API
- Embedded Service Chat
- Gmail and Outlook integration
Unsupported Features
- Salesforce Console APIs (Navigation item API, Workspace API, Utility Bar API)
- URL Addressable Tabs
- Conversation Toolkit API, Omni Toolkit API, Quick Action API
- Standard Action Overrides, Custom Actions, Global Actions, List View Actions, Related List View Actions
- Chatter Extensions
Supported JavaScript
Lightning Web Components JavaScript Support includes:
- ES6 (ECMA Script 2015)
- ES7 (ECMA Script 2016)
- ES8 (ECMA Script 2017) – Excluding shared Memory and Atomics
- ES9 (ECMA Script 2018)- Including only Object Spread Properties (not Object Rest Properties)
Next Post
How to Choose – Lightning Web Components OR AURA
Thank you for visiting Our Blog ,click on Follow get the updates quickly...
.png)
.png)
.png)
.png&description=Difference Between LWC & AURA ){kind=link}
0 Comments