Socket
Socket
Sign inDemoInstall

@vonage/vvd-core

Package Overview
Dependencies
Maintainers
13
Versions
124
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@vonage/vvd-core - npm Package Compare versions

Comparing version 2.6.2 to 2.7.0

9

CHANGELOG.md

@@ -0,1 +1,10 @@

# [2.7.0](https://github.com/vonage/vivid/compare/v2.6.2...v2.7.0) (2021-05-17)
### Bug Fixes
* **docs:** viv-375 added init flow and core dependencies ([#821](https://github.com/vonage/vivid/issues/821)) ([903c1f6](https://github.com/vonage/vivid/commit/903c1f643f50f249c94b9d82aca3b55d6164bc04))
## [2.6.2](https://github.com/vonage/vivid/compare/v2.6.1...v2.6.2) (2021-05-05)

@@ -2,0 +11,0 @@

10

package.json
{
"name": "@vonage/vvd-core",
"version": "2.6.2",
"version": "2.7.0",
"description": "> TODO: description",

@@ -30,11 +30,11 @@ "author": "yinonov <yinon@hotmail.com>",

"dependencies": {
"@vonage/vvd-fonts": "2.6.2",
"@vonage/vvd-scheme": "2.6.2",
"@vonage/vvd-fonts": "2.7.0",
"@vonage/vvd-scheme": "2.7.0",
"tslib": "^2.0.3"
},
"devDependencies": {
"@vonage/vvd-umbrella": "2.6.2",
"@vonage/vvd-umbrella": "2.7.0",
"typescript": "^4.1.3"
},
"gitHead": "13d4bbb0e9cf0539225cfcbd6c977aa75f1e5e0f"
"gitHead": "e62d8e6de16985a77757a01db255933fdb9d6f7a"
}

@@ -1,5 +0,5 @@

### Core - Vivid overlay lifecycle
### Core - Vivid lifecycle
Vivid content may be consumed on different levels.
One may consume a single component, like `vwc-button`.
One may consume a single component, like `vwc-button`, `vwc-dialog` etc.
Another use might be to init a common context via `vvd-context` service to style a common HTML native semantics like `H1`, `p` etc.

@@ -11,4 +11,12 @@

There is a lifecycle here.
We've designed Vivid overlay lifecycle to be self-contained, agnostic to other contexts and to not interfere nor require alignment to the existing application lifecycle or any other framework in place.
We've designed Vivid lifecycle to be self-contained, agnostic to other contexts and to not interfere nor require alignment to the existing application lifecycle or any other framework in place.
The chart below represents a general runtime initialization flow, while separating the system into the consumer-visible realm and the underlying platform.
Consumer realm's items are to be consumed by the hosting applications directly (API / imports etc). Below the line are the core parts of our system which are transparent to the consumer in vast majority of cases.
![Flow chart](assets/vivid-core-flow.svg)
#### Initialization flavors
__vivid core__ initialization may go 2 main paths:

@@ -46,3 +54,3 @@ - __auto-init__: this is the default behavior, Vivid will auto init itself upon the first usage unless specified otherwise

In order to help Vivid overlay to initialize itself to some specific state, consuming application should use `data-vvd-context` attribute on `html` element.
In order to help Vivid to initialize itself to some specific state, consuming application should use `data-vvd-context` attribute on `html` element.
The below example will auto-initialize __vivid core__ with the dark theme.

@@ -86,2 +94,2 @@

> Reminder: `settled` Promise of the __vivid core__ is immediately rejected when __none__ initialization flavor is used.
> Reminder: `settled` Promise of the __vivid core__ is immediately rejected when __none__ initialization flavor is used.
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc