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

@nuvler/theme-sdk

v1.3.2

Published

Contrato público para temas da plataforma Nuvler

Readme

@nuvler/theme-sdk

Contrato público compartilhado entre temas Nuvler e o Store.

import { defineTheme, THEME_API_VERSION, THEME_RUNTIME_VERSION } from "@nuvler/theme-sdk";

export const theme = defineTheme({
  manifest: {
    schemaVersion: 1,
    id: "meu-tema",
    name: "Meu tema",
    version: "1.0.1",
    runtimeVersion: THEME_RUNTIME_VERSION,
    sdkVersion: `^${THEME_API_VERSION}`,
    entry: "src/theme.tsx",
    styles: ["src/theme.css"],
    presentation: {
      description: "Tema da minha loja",
      colors: {
        primary: "#1d4ed8", primaryText: "#ffffff",
        secondary: "#f59e0b", secondaryText: "#0f172a", accent: "#d97706",
        background: "#f8fafc", surface: "#ffffff", surfaceAlt: "#f1f5f9",
        text: "#0f172a", textMuted: "#64748b", border: "#e2e8f0",
        headerBackground: "#ffffff", headerText: "#0f172a",
        footerBackground: "#0f172a", footerText: "#f8fafc",
      },
      layout: { containerWidth: 1200, borderRadius: 16 },
    },
  },
  // tokens, template e components
});

version identifica a versão imutável do tema. runtimeVersion identifica o protocolo mount/unmount e sdkVersion declara a faixa do SDK aceita.

primary, secondary, background e text permanecem obrigatórios para compatibilidade. Os demais tokens semânticos são opcionais no contrato, mas o starter atual já os declara e os runtimes aplicam fallbacks para temas antigos.

Use productUrl(product) ao gerar links de produto. Quando categoryPath estiver presente, a URL inclui toda a hierarquia da categoria principal; com APIs antigas, o helper mantém o fallback /produto/slug.

Componentes da Home declarados pelo tema

Na Theme API 1.3, manifest.presentation.homeComponents declara componentes que o Gestão pode editar sem conhecer previamente sua implementação. Cada seção usa type: "theme-component" e carrega componentKey, schemaVersion e props. Formulários usam a ação segura contact.submit e recebem a função em HomeProps.submitContact ou ThemeRuntimeSdk.contact.submit.

O contrato completo e os exemplos estão em docs/dynamic-home-components.md.