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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@strictly-lang/compiler

v1.4.0

Published

a compiler for the programming language strictly

Downloads

4

Readme

strictly

About

strictly is a declarative programming language for interactive web-uis.

Goals

  • Correctness
    • through type typesafety and immutability
    • through the declarative paradigm
  • Safety
    • the compiler will protect you from xss
  • Performance
    • no shadow dom diffing, all change paths are optimized at compile time
    • small memory footprint, therefore less garbage-collection freezes
  • Size
    • there is no framework or runtime involved, everything is encapsulated inside the web component
  • small scope
    • no feature-creep
    • this language is aimed to solve dom interactions and state handling, not more not less

Tradeoffs

  • limited browser support
    • strictly is based on webcomponents
    • no walkarounds for outdated browser bugs
  • no JS interop
    • there is no plan to make Javascript interoparability possible
    • the only interaction is through the webcomponent-api
  • no ecosystem
    • no integration to js libraries
    • no integration to css libraries
  • no feature richness
    • the scope of this language is very small and aims to solve only a limited scope

State

This project is currently in its very early stages, the featureset and the apis will change.