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

elderjs-esbuild

v0.0.4

Published

A very PoC tool to build Elder.js sites faster with esbuild

Downloads

14

Readme

Elder.js esbuild

This is a tool I'm using on my own projects. It will change, it will break, I may even abandon it, use it at your own risk.

In your elder.js project:

  1. npm i --save elderjs-esbuild
  2. create bundle.js with require('elderjs-esbuild').default();
  3. node bundle.js

todo:

  • [ ] hashed components (esbuild is tracking)
  • [ ] look at adding an additional export with _css to see if we can match Elder.js's current output. (basically impossible with current api)
  • [x] clean folder on initial build.
  • [x] remove dependencies/css on deletion of a svelte file.
  • [x] move css to a cache with sourcemaps instead of reading them from the file.
  • [x] modules with exported svelte files.
  • [x] rebundle the entire dependency tree on sub module change. (elder.js plugins with templates can use this same pattern.)
  • [x] clean up memory of caches.
  • [x] basic preprocess support....
  • [x] make sure that the css file is emitted to the right folder.