npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@lwc/engine-core

v8.9.0

Published

Core LWC engine APIs.

Downloads

24,059

Readme

@lwc/engine-core

This package contains the core logic shared by different runtime environments. Examples of this include the rendering engine and the reactivity mechanism. Since this package only provides internal APIs for building custom runtimes, it should never be consumed directly in an application.

Usage of internal APIs are prevented by the compiler and are therefore not documented here.

Supported APIs

This package supports the following APIs.

@api

This decorator is used to mark the public fields and the public methods of an LWC component.

import { LightningElement, api } from 'lwc';

class LightningHello extends LightningElement {
    @api
    hello = 'default hello';
}

@track

This decorator should be used on private fields to track object mutations.

import { LightningElement, api, track } from 'lwc';

class LightningHello extends LightningElement {
    @api
    get name() {
        return name.raw;
    }
    set name(value) {
        name.normalized = normalize(value);
    }

    @track
    name = {
        raw: 'Web components ',
        normalized: 'Web Components',
    };
}

@wire

This decorator should be used to wire fields and methods to a wire adapter.

import { LightningElement, wire } from 'lwc';
import { getRecord } from 'recordDataService';

export default class Test extends LightningElement {
    @wire(getRecord, { id: 1 })
    recordData;
}

createContextProvider()

This function creates a context provider, given a wire adapter constructor.

LightningElement

This class should be extended to create an LWC constructor.

import { LightningElement } from 'lwc';

class LightningHello extends LightningElement {
    // component implementation
}

Experimental APIs

Experimental APIs are subject to change, may be removed at any time, and should be used at your own risk!

getComponentDef()

This experimental API provides access to internal component metadata.

isComponentConstructor()

This experimental API enables the identification of LWC constructors.

readonly()

This experimental API enables the creation of a reactive readonly membrane around any object value.

setHooks()

This experimental API allows setting overridable hooks with an application specific implementation.

List of overridable hooks:

  1. sanitizeHtmlContent, see sanitizeHtmlContent.

sanitizeAttribute()

This experimental API enables the sanitization of HTML attribute values by external services.

sanitizeHtmlContent()

This experimental API enables the sanitization of HTML content by external services. The lwc:inner-html binding relies on this hook. This hook must be overridden (see setHooks ) as the default implementation is to throw an error.

unwrap()

This experimental API enables the removal of an object's observable membrane proxy wrapper.

setTrustedSignalSet()

This experimental API enables the addition of a signal as a trusted signal. If the ENABLE_EXPERIMENTAL_SIGNALS feature is enabled, any signal value change will trigger a re-render.

If setTrustedSignalSet is called more than once, it will throw an error. If it is never called, then no trusted signal validation will be performed. The same setTrustedSignalSet API must be called on both @lwc/engine-dom and @lwc/signals.