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

physics-lib

v1.0.0

Published

My new Decentraland project

Downloads

3

Readme

Example of decentraland library

It uses a modified version of build-ecs to build and import the assets. It does not work with @next or @latest yet.

For the demonstration, all compiled assets are committed to this repository. (dist folder)

What is the value in decentraland libraries?

Without this change, creating libraries has several limitations and corner cases.

  1. Libraries can only exist if the original sources are commited. Then it is necessary to "fool" typescript to include the sources from relative paths because CommonsJS is missing in our AMD context.
  2. Bunding and reusing libraries is very difficult or dangerous. It can be made embeding a .js file with proper typings .d.ts. But it is a horrible hack.
  3. To reuse the ECS capabilities to create i.e. Systems or Components, nowadays packages need to either build in a special way to not embed the ECS itself (there is no tooling for it yet) or commit the raw .ts sources.
  4. As mentioned in (1), there is no module resolution schemas for this kind of builds. There are only files, and to include something installed in node_modules, you must use relative paths import { .. } from '../../../../node_modules/eth-connect/eth-connect.esm' which is obviously, far from being the ideal case.