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

@quenty/loader

v10.7.1

Published

A simple module loader for Roblox

Downloads

4,793

Readme

Loader

A simple module loader for Roblox

Installation

npm install @quenty/loader --save

Installation with NPM

Install via NPM like this:

npm install @quenty/loader --save

New features and requirements

  1. Convert between NPM and Wally format
    1. Replicate/build out correct models
    2. Preserve single script instance for debugging
    3. Create bounces
  2. Convert between Wally format and Nevermore original format
  3. Understand object values at the NPM level -> Wally format

Bootstrapping

local LoaderUtils = require(ServerScriptService.Modules:FindFirstChild("LoaderUtils", true))
LoaderUtils.toWallyFormat(ServerScriptService.Modules, {
	Client = ReplicatedStorage;
	Shared = ReplicatedStorage;
	Server = ServerScriptService;
})

Algorithm

We assume is a folder is a package if it contains a "dependencies" folder. For a given package folder, all packages underneath it shall have...

  1. Access to every other package that is not in the dependencies folder
  2. Access to every package in the dependency folder at the 1st level of recursion
  3. Access to every package in the dependency folder at each ancestor level at the 1st level of recursion
  4. Access to every sibling package (this is because we expect to be installed at a uniform level)

  • A module will be defined by a module script

  • A junction will be defined by a place with a "Dependencies" folder and will have access to its dependency folder, and all ancestors, but not siblings

  • A junction will give all modules underneath it access

  • Modules expect external dependencies to be at script.Parent

  • Modules will be split between client/server/shared based upon their parent

  • Dependencies will be any modules up to the root

  • For conflicts, the first copy available will be used (Start at a tree, go up one node, and look all the way down for a copy)

  • Modules will prefer to be parented directly, at a top level, without a bouncer

    • However, if a requirement is needed at a separate version, the module will be parented to its own folder, and a bounce script will point to it.
    • All required modules that it may need will point back to this module.
  1. Discover junctions and
  2. If there are no conflicts, then just link the shared modules for the server to consume, and we're done.
  3. If there are conflicts, than we need to build 2 trees for each conflict.
    1. Identify junction
		A
	B		C
Maid1	Other	Maid2