Almost all of us started using LWC instead of Aura or Visualforce however there are multiple occasion where we need to come back to either Aura or Visualforce.
I was not able to find single consolidated list of limitations of LWC and therefore thought to post this blog.
Feel free to comment on this blog post and help me keep this updated.
Unsupported features of Lightning Web Components
- Overriding standard buttons like Create, Edit & View
- Custom Actions
- Global Actions
- List View Actions
- Related List View Actions
- Lightning Out [Beta]
- Rendering LWC as PDF Page
- Using LWC in Email Templates
- Console APIs (Navigation Item API, Workspace API, Utility Bar API)
- Chatter Action
- Conversation Toolkit API
- Omni Toolkit API
- Quick Action API
Thanks Jitendra. Good to know about this.
Hi Jitendra,
I was looking for an article like this. Thank you for the great information.
Quick questions, most of these shortcomings can be taken care of by embedding LWC is Aura components right?
Thanks for the info, I think Quick Action API will be available from next release, not sure.