Security News
JavaScript Leaders Demand Oracle Release the JavaScript Trademark
In an open letter, JavaScript community leaders urge Oracle to give up the JavaScript trademark, arguing that it has been effectively abandoned through nonuse.
@lion/core
Advanced tools
The @lion/core
package is mostly for in depth usage.
It handles the version of lit-element
and lit-html
.
In order to be sure a compatible version is used import it via this package.
import { LitElement, html, render } from '@mdjs/mdjs-preview';
These features are not well documented - care to help out?
npm i --save @lion/core
import { dedupeMixin, LitElement } from '@mdjs/mdjs-preview';
const BaseMixin = dedupeMixin((superClass) => {
return class extends superClass { ... };
});
Imagine you are developing web components and creating ES classes for Custom Elements. You have two generic mixins (let's say M1
and M2
) which require independently the same even more generic mixin (BaseMixin
). M1
and M2
can be used independently, that means they have to inherit from BaseMixin
also independently. But they can be also used in combination. Sometimes M1
and M2
are used in the same component and can mess up the inheritance chain if BaseMixin
is applied twice.
In other words, this may happen to the protoype chain ... -> M2 -> BaseMixin -> M1 -> BaseMixin -> ...
.
An example of this may be a LocalizeMixin
used across different components and mixins. Some mixins may need it and many components need it too and can not rely on other mixins to have it by default, so must inherit from it independently.
The more generic the mixin is, the higher the chance of being appliend more than once. As a mixin author you can't control how it is used, and can't always predict it. So as a safety measure it is always recommended to create deduping mixins.
This is an example of how to make a conventional ES mixin deduping.
const BaseMixin = dedupeMixin((superClass) => {
return class extends superClass { ... };
});
// inherits from BaseMixin
const M1 = dedupeMixin((superClass) => {
return class extends BaseMixin(superClass) { ... };
});
// inherits from BaseMixin
const M2 = dedupeMixin((superClass) => {
return class extends BaseMixin(superClass) { ... };
});
// component inherits from M1
// MyCustomElement -> M1 -> BaseMixin -> BaseCustomElement;
class MyCustomElement extends M1(BaseCustomElement) { ... }
// component inherits from M2
// MyCustomElement -> M2 -> BaseMixin -> BaseCustomElement;
class MyCustomElement extends M2(BaseCustomElement) { ... }
// component inherits from both M1 and M2
// MyCustomElement -> M2 -> M1 -> BaseMixin -> BaseCustomElement;
class MyCustomElement extends M2(M1(BaseCustomElement)) { ... }
FAQs
Core functionality that is shared across all Lion Web Components
The npm package @lion/core receives a total of 12,031 weekly downloads. As such, @lion/core popularity was classified as popular.
We found that @lion/core demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In an open letter, JavaScript community leaders urge Oracle to give up the JavaScript trademark, arguing that it has been effectively abandoned through nonuse.
Security News
The initial version of the Socket Python SDK is now on PyPI, enabling developers to more easily interact with the Socket REST API in Python projects.
Security News
Floating dependency ranges in npm can introduce instability and security risks into your project by allowing unverified or incompatible versions to be installed automatically, leading to unpredictable behavior and potential conflicts.