Lightning Web Component Best

Practices
Mohith Shrivastava, Lead Developer Advocate
@msrivastav13 | mohith.shrivastava@salesforce.com
He/Him
Forward Looking Statements
This presentation contains forward-looking statements about, among other things, trend analyses and future events, future financial performance, anticipated growth, industry prospects,
environmental, social and governance goals, and the anticipated benefits of acquired companies. The achievement or success of the matters covered by such forward-looking statements involves
risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions prove incorrect, Salesforce’s results could differ materially from the results expressed or
implied by these forward-looking statements. The risks and uncertainties referred to above include those factors discussed in Salesforce’s reports filed from time to time with the Securities and
Exchange Commission, including, but not limited to: impact of, and actions we may take in response to, the COVID-19 pandemic, related public health measures and resulting economic downturn
and market volatility; our ability to maintain security levels and service performance meeting the expectations of our customers, and the resources and costs required to avoid unanticipated
downtime and prevent, detect and remediate performance degradation and security breaches; the expenses associated with our data centers and third-party infrastructure providers; our ability to
secure additional data center capacity; our reliance on third-party hardware, software and platform providers; the effect of evolving domestic and foreign government regulations, including those
related to the provision of services on the Internet, those related to accessing the Internet, and those addressing data privacy, cross-border data transfers and import and export controls; current and
potential litigation involving us or our industry, including litigation involving acquired entities such as Tableau Software, Inc. and Slack Technologies, Inc., and the resolution or settlement thereof;
regulatory developments and regulatory investigations involving us or affecting our industry; our ability to successfully introduce new services and product features, including any efforts to expand
our services; the success of our strategy of acquiring or making investments in complementary businesses, joint ventures, services, technologies and intellectual property rights; our ability to
complete, on a timely basis or at all, announced transactions; our ability to realize the benefits from acquisitions, strategic partnerships, joint ventures and investments, including our July 2021
acquisition of Slack Technologies, Inc., and successfully integrate acquired businesses and technologies; our ability to compete in the markets in which we participate; the success of our business
strategy and our plan to build our business, including our strategy to be a leading provider of enterprise cloud computing applications and platforms; our ability to execute our business plans; our
ability to continue to grow unearned revenue and remaining performance obligation; the pace of change and innovation in enterprise cloud computing services; the seasonal nature of our sales
cycles; our ability to limit customer attrition and costs related to those efforts; the success of our international expansion strategy; the demands on our personnel and infrastructure resulting from
significant growth in our customer base and operations, including as a result of acquisitions; our ability to preserve our workplace culture, including as a result of our decisions regarding our current
and future office environments or work-from-home policies; our dependency on the development and maintenance of the infrastructure of the Internet; our real estate and office facilities strategy
and related costs and uncertainties; fluctuations in, and our ability to predict, our operating results and cash flows; the variability in our results arising from the accounting for term license revenue
products; the performance and fair value of our investments in complementary businesses through our strategic investment portfolio; the impact of future gains or losses from our strategic
investment portfolio, including gains or losses from overall market conditions that may affect the publicly traded companies within our strategic investment portfolio; our ability to protect our
intellectual property rights; our ability to develop our brands; the impact of foreign currency exchange rate and interest rate fluctuations on our results; the valuation of our deferred tax assets and
the release of related valuation allowances; the potential availability of additional tax assets in the future; the impact of new accounting pronouncements and tax laws; uncertainties affecting our
ability to estimate our tax rate; uncertainties regarding our tax obligations in connection with potential jurisdictional transfers of intellectual property, including the tax rate, the timing of the transfer
and the value of such transferred intellectual property; uncertainties regarding the effect of general economic and market conditions; the impact of geopolitical events; uncertainties regarding the
impact of expensing stock options and other equity awards; the sufficiency of our capital resources; the ability to execute our Share Repurchase Program; our ability to comply with our debt
covenants and lease obligations; the impact of climate change, natural disasters and actual or threatened public health emergencies; and our ability to achieve our aspirations, goals and projections
related to our environmental, social and governance initiatives.

Updated: September 28, 2022

Thank
you
Agenda

● How to compose your components

● Best Practices of building reusable components

● Best practices for component communication

● How to style your reusable component

● Error Handling Patterns

● Performance Best Practices

● Security best practices

Composition
Balance modularity and reusability
 Composing an App Page

Base
Components Standard or
(A classic example Custom
of reusable Components
components)
Page
How to compose your components?
Mantra - Do not over modularize

1. Can the component use

Salesforce base components? Base Components provide below features
2. Does your organization maintain ● Abstracted
a set of reusable components? ● Provides lots of features and
3. Is there an opportunity to find functionality via attributes
something reusable? ● Built in SLDS
● You can custom style them using
hooks
● Accessible
Reusable Component
Dividing Components
Dividing Components - Level 1- Based on
Functionality
Dividing Components - Level 1- Based on
Functionality
Dividing Components - Level 2 - Based on
Reusability

productTile
Dividing Components - Level 2 - Based on
Reusability

productTile
Characteristics of a Reusable Component

● A Reusable Component is dumb as possible

● Has well documented public properties, public
functions and events
● Favors public properties over public methods
Component Variations
Static variation
Desktop View Mobile View

For component variations that are structurally different, use multiple

templates.
Component Variations
Dynamic variation

Use Slots to create component variants, when structure is dynamic.

Slot Example
Designing components for App Builder
Mantra - Strike balance between number of components vs Loose coupling

● Is it really worth breaking the components for app builder?

○ App Builder allows you to compose components but if you try

to overuse it you end up with lots of pub sub events or LMS

○ Lots of pub sub or LMS will cause performance issues

Component
Communication
Best Practices for using LWC
Events
Communicating via Events Best Practices
Props down and events up
Communicating via Events Best Practices (In Same
DOM Hierarchy)
Props down and events up

Trailhead Module to practice

Events Best Practices
Communicating via Events Best Practices
Custom Events Best Practices

When using Custom Events make sure you pass only primitive types in detail object
Communicating via Events Best Practices
Custom Events Best Practices
For communication of data in same shadow tree do not add property into the
event.detail. The consumer can use event.target.myproperty
Communicating via Events Best Practices
Custom Events Best Practices
Communicating via Events Best Practices
Custom Events Best Practices

1. For communication of data not in same shadow tree use event.detail

2. Use events configured with bubbles: false and composed: false

a. They're the least disruptive. These events don’t bubble up through the DOM and don’t cross
the shadow boundary.
Communicating via Events Best Practices
Cross DOM Communication
Communicating via Events Best Practices
Use Redux to manage events and state of your app (Applicable if your
component comprises of large number of events)
Producer Producer Producer Producer Producer Producer

Consumer Consumer Consumer Consumer Consumer Consumer

Producer Producer Producer Producer Producer Producer

Sample Repo with Redux

implemented for LWC
Redux
Store

Consumer Consumer Consumer Consumer Consumer Consumer

Styling Reusable
Components
Use Styling hooks and css
custom properties
Styling Reusable Components

LWC encapsulates and isolates a component’s stylesheet.

Styling Reusable Components

● Use CSS Custom Properties for custom styles

● Use Styling Hooks to override styling of Base Components.

● Favor Styling Hooks and CSS Custom Properties over component attributes.
Error Handling Best
Practices
Common Error Handling Utility
component
Error Handling

● Adopt a common error reporting strategy for your

components.

● If your component is not standalone, throw errors to the

parent component.
Example of a common error
● Create a reusable errorPanel component across the handler component from
lwc-recipes

entire project.
Performance Best
Practices
Improving LWC Performance

● Use Lightning Data Service or cached data or ui adaptor

● If multiple component retrieve the same data create a utility component

● Lazy load the Data

● Fine tune your SOQL query if using it

● Progressive rendering

Trailhead module for LWC

Performance best practices
Security Best Practices
Security Best Practices

● Plan for enabling LWS if you have not yet enabled.

○ Offers built in capabilities like HTML sanitization and blocks code that

violates CSP

○ Supports additional features like cross namespace lwc modules,

● Minimize third party library

○ If used simply use the platformResourceLoader module

● Adopt Principle of least privilege. composable: false and Trailhead module for LWC
Security best practices
bubbles:false for events

● Avoid use of DOM manipulation or using lwc=”manual”

Security Best Practices
If DOM manipulation is used avoid below APIs.

SetTimeout

SetInterval

Eval

DOMParser.parseFromString
Trailhead module for LWC
Security best practices
Document.implementation.createHTMLDocument
Thank you