Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@benev/slate

Package Overview
Dependencies
Maintainers
0
Versions
74
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@benev/slate - npm Package Versions

1
8

0.1.0-x.5

Diff

chasemoskal
published 0.1.0-x.4 •

chasemoskal
published 0.1.0-x.3 •

chasemoskal
published 0.1.0-x.2 •

chasemoskal
published 0.1.0-x.1 •

chasemoskal
published 0.0.0 •

Changelog

Source

v0.0.0

in this recent work, the flat and signals state management apis are converging.

  • 🟥 removed synonyms slate.carbon, slate.oxygen, slate.obsidian, slate.quartz
    • now you should use slate.shadow_component, slate.light_component, slate.shadow_view, slate.shadow_component respectively
  • 🟥 flat breaking changes
    • removed .manual, .auto, .deepReaction
    • flat now implements ReactorCore
      • .reaction always has debouncing and discovery enabled
      • .wait to wait for the debouncer to fire responders
      • .lean for advanced integrations
  • 🟥 signals breaking changes
    • removed .track (now you should use .reaction instead)
    • signals now implements ReactorCore
      • .reaction always has debouncing and discovery enabled
      • .wait to wait for the debouncer to fire responders
      • .lean for advanced integrations
  • 🔶 the way reactivity works has been rewritten, so be wary of new bugs
    • the flatstate and signals mixins have been rewritten using the new .lean methods
    • the internal setup_reactivity for slate components and views has been rewritten using the reactor's .lean
  • 🍏 added new state management system called reactor
    • implements ReactorCore (has .reaction, .wait, and .lean)
    • reactor combines both flatstate and signals reactivity
    • so you can make reactions that listen to both flatstates and signals
    • see usage examples in the readme
  • 🍏 added new mixin.reactor and apply.reactor
    • this is how you can mixin reactor support for your own elements, thus adding reactivity for both flatstate and signals at once
  • note, there are no changes to watch
    • watch is fundamentally different than flatstate and signals, and is not suitable to become a ReactorCore
    • watch does not have any "automated" reactivity, it's always explicit, so it has .track instead of .reaction
<br/>
chasemoskal
published 0.0.0-dev.29 •

chasemoskal
published 0.0.0-dev.28 •

Changelog

Source

v0.0.0-dev.28

  • 🟥 change Initiator signature, added .cleanup helpers
chasemoskal
published 0.0.0-dev.27 •

Changelog

Source

v0.0.0-dev.27

  • 🟥 replace WatchBox with Signal
  • 🟥 WatchTower now requires SignalTower as a param
  • 🍏 add exports 'flatstate' and 'signal'
  • 🍏 add ZipAction.prep, ZipAction.prepAction, ZipAction.prepBlueprint
chasemoskal
published 0.0.0-dev.26 •

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