Contents
There are three main ways to share JavaScript code among your Lightning Components developed with the Aura programming model that I want to touch on in this blog post and how Lightning Locker Service and the Freeze JavaScript Prototypes (new in Winter ’19) setting may affect which option you choose.
Why are JavaScript prototypes freezing in Lightning aura?
Freezing JavaScript prototypes prevents Lightning component authors from modifying JavaScript prototypes of global objects that are shared between namespaces. This restriction enables better code separation between components and prevents malicious or inadvertent tampering of shared objects, such as the JavaScript APIs or DOM APIs.
How to use lightning message service in JavaScript?
Communicating Across the DOM with Lightning Message Service Creating Apps Styling Apps Developing Secure Code Using JavaScript Supported JavaScript Invoking Actions on Component Initialization
What do you need to know about lightning aura?
Lightning Aura Components APIs All Documentation Learn Trailhead Certification Sample Gallery Podcast Video Gallery Events and Webinars
How to reproduce an aura component in JavaScript?
To reproduce, all you need is a component with an aura:attribute like so: The Javascript controller reveals the interesting behavior:
How to determine a variable type in Lightning aura?
Setting a default value without square brackets is deprecated and can lead to unexpected behavior. To determine a variable type, use typeof or a standard JavaScript method, such as Array.isArray () , instead. The instanceof operator is unreliable due to the potential presence of multiple windows or frames.
Why does Lightning Aura return a proxy object?
Lightning Aura attributes returns proxy objects from components of API > 40. This is because Lightning Locker Uses the Proxy Object. You can interact with a Proxy object in the same way as you interact with the raw JavaScript object, but the object shows up in the browser’s console as a Proxy.