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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@libs-scripts-mep/detectors

v1.4.3

Published

Abra o terminal, e na pasta raíz do script, execute:

Downloads

238

Readme

Detectors 🔎

Instalando

Abra o terminal, e na pasta raíz do script, execute:

npm i @libs-scripts-mep/detectors

Desinstalando

Abra o terminal, e na pasta raíz do script, execute:

npm uninstall @libs-scripts-mep/detectors

Atualizando

Abra o terminal, e na pasta raíz do script, execute:

npm update @libs-scripts-mep/detectors

Uso básico

A biblioteca fornece duas classes principais:

  • Detector → responsável por criar detectores digitais ou analógicos.
  • DetectorRunner → responsável por executar a detecção e controlar o ciclo before → detect → after.

Criando um detector digital

import { Detector } from "@libs-scripts-mep/detectors"
import { DetectionMode } from "@libs-scripts-mep/detectors/test-types.js"

// Exemplo: detector digital que dispara na transição RISING
const detector = Detector.createDigital(
  "Reed Switch",           // Nome do circuito
  { value: false },        // Objeto observado
  DetectionMode.RISING,    // Modo de detecção
  5000                     // Timeout em ms
)

Modos disponíveis para digitais:

  • INSTANT → verifica valor instantâneo (true ou false).
  • RISING → detecta transição de false → true.
  • FALLING → detecta transição de true → false.
  • CHANGE → detecta qualquer mudança de estado.
  • HOLD → verifica se o valor permanece por um certo tempo.

Criando um detector analógico

import { Detector } from "../node_modules/@libs-scripts-mep/detectors/detectors.js"
import { DetectionMode } from "../node_modules/@libs-scripts-mep/detectors/test-types.js"

// Exemplo: detector analógico que exige manter valor por 1000ms
const detector = Detector.createAnalog(
  "Battery",
  { value: 23.8 },
  24,              // Valor esperado
  1,               // Tolerância
  DetectionMode.HOLD,
  5000,            // Timeout
  1000             // Hold em ms
)

Modos disponíveis para analógicos:

  • INSTANT → verifica valor instantâneo.
  • HOLD → verifica se o valor permanece por um certo tempo.

Executando a detecção completa (lifecycle before → detect → after)

import { DetectorRunner } from "../node_modules/@libs-scripts-mep/detectors/detectors.js"

async function testFunction() {
  const digitalDetector = Detector.createDigital("Relay RL1", { value: false }, DetectionMode.RISING, 5000)

  const result = await DetectorRunner.run(
    digitalDetector,
    () => console.log("➡️ Antes da detecção"),
    async () => {
      // Simula trigger externo que muda o valor
      setTimeout(() => digitalDetector.inputRef.value = true, 1000)
    },
    () => console.log("✅ Depois da detecção")
  )

  console.log(result)
}

testFunction()

Executando apenas a detecção

import { Detector } from "../node_modules/@libs-scripts-mep/detectors/detectors.js"

async function testFunction() {
  const digitalDetector = Detector.createDigital("Relay RL1", { value: false }, DetectionMode.RISING, 5000)

  const result = await digitalDetector.detect()

  console.log(result)
}

testFunction()

Resultado da detecção

Se a detecção for bem-sucedida, o detection irá conter os dados da detecção:

{
  "error": null,
  "detection": {
    "success": true,
    "circuitName": "Relay RL1",
    "timestamp": 1699999999999,
    "message": "Transição RISING detectada"
  }
}

Se a detecção falhar, o detection irá conter os dados da detecção:

{
  "error": null,
  "detection": {
    "success": false,
    "circuitName": "Relay RL1",
    "timestamp": 1699999999999,
    "message": "Transição RISING não detectada no tempo limite"
  }
}

Se a detecção falhar (exception), o error irá conter uma mensagem de erro:

{
  "error": "Uncaught Error: ❌...",
  "detection": null
}