Tool Suite for Aura Components Development

Browser: Google Chrome
Many web app developers use Google Chrome because of its excellent developer tools. If that describes you, you’re done. Next item.

Browser Debugger: Chrome DevTools

If you’re not already confident using Chrome DevTools, we highly, highly recommend the outstanding docs available. Start with Getting Started, and then move to the training, beginning with DevTools Overview. Every minute you spend learning to use DevTools is 10 minutes you’ll save later. (The payoff is more like 50-to-1, but we’ll be conservative.)

DevTools Extension: Salesforce Lightning Inspector

Developing for Aura components without the Salesforce Lightning Inspector is like starting a fire by rubbing sticks together. You can do it, but it’s exercise, and who wants that?

What’s special about the Lightning Inspector? With this plug-in for DevTools, you can navigate the component tree, inspect component attributes, and profile component performance. You can observe and inspect calls to server-side actions and their responses. And it helps you understand the sequence of event firing and handling. (We explain all these terms in the next module on this trail, Aura Components Core Concepts.)

Editor: Visual Studio (VS) Code with Salesforce Extension Pack
Salesforce offers two editors with dedicated tooling for Aura components. While Developer Console is fine for quick edits and small scale learning projects, including this module, it’s not the best tool for developing real components and apps.

The best tool is VS Code. Once you’ve installed VS Code, add Salesforce CLI and the Salesforce Extensions for VS Code, which adds dedicated navigation, syntax highlighting, and other Aura components-specific features to VS Code. The combination gives you a world-class development environment for Aura components work.

Reference: https://trailhead.salesforce.com/content/learn/modules/lex_dev_lc_vf_fundamentals

Governor limits in Salesforce

Governor limits are runtime limits enforced by the Apex runtime engine. Since Apex runs in a shared, multitenant environment, the Apex runtime engine strictly enforces a number of limits to ensure that code does not monopolize shared resources.

Types of limits that Apex enforces are resources like

1. Memory

2. Database resources

3. The number of script statements to avoid infinite loops

4. The number of records being processed.

If code exceeds a limit, the associated governor issues a runtime exception. Because Apex runs in a multitenant environment, the Apex runtime engine strictly enforces a number of limits to ensure that runaway Apex doesn’t monopolize shared resources.

If some Apex code ever exceeds a limit, the associated governor issues a runtime exception that cannot be handled.

The Apex limits, or governors, track and enforce the statistics outlined in the following tables and sections.

1. Per-Transaction Apex Limits

2. Per-Transaction Certified Managed Package Limits

3. Force.com Platform Apex Limits

4. Static Apex Limits

5. Size-Specific Apex Limits

6. Miscellaneous Apex Limits

The good:

Governor limits prevent other organisation from writing bad code and taking up all the cloud CPU.
Coding limits, in general, are completely unique to Apex – consider it job security!
You have a friend that will teach you how to dominate these limits!

The bad:

These are hard limits on your org preventing you, for example, from doing too many SOQL queries in a trigger (max: 100 queries).
Upgrading your edition or paying Salesforce more money will not increase your limits! The only workaround is to understand how to navigate around them.

Please check below links. I hope that will help you

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm

 

Lightning Web Components

Lightning Web Components is a new programming model for building Lightning components. It leverages web standards breakthroughs, can coexist and interoperate with the Aura programming model and delivers unparalleled performance.

To create and develop Lightning Web Components and leverage their powerful features and performance benefits, you need to set up Salesforce DX.

For this Quick Start, you also use the Visual Studio Code, which is the recommended Salesforce development environment. Once your developer environment is ready, you learn how to write a simple Lightning web component and add it to a page in Lightning Experience.

Lightning Web Components uses core Web Components standards and provides only what’s necessary to perform well in browsers supported by Salesforce. Because it’s built on code that runs natively in browsers, Lightning Web Components is lightweight and delivers exceptional performance.

Most of the code you write is standard JavaScript and HTML.

References:

  1. Quick Start: Lightning Web Components
  2. Design attributes in Lightning Web Components | CSS and SVG Files | Lightning Web Components
  3. Introducing Lightning Web Components