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

@rbxts/flamework-di-toolkit

v1.1.0

Published

Library that buffs flamework dependency injection system

Readme

💉 flamework dependency injection toolkit

Library that buffs flamework dependency injection system

✒️ Credits

SUMER (discord sumer_real): for creating this library

🌠 Install

npm install @rbxts/flamework-di-toolkit

📚 Documentation

Inject marker

first thing you need to do is to mark fields you need to inject

export type Version = string;

export class MyClass {
	@Inject()
	public version: Version;
}

DependencyContainer

this used to inject dependencies

const container = new DependencyContainer();

container.register<Version>("1.0");  // firstly you need to register all dependencies

print(container.resolve<Version>());  // will output -> 1.0

// there two ways to inject into classes

// first way is to inject into constructed class
const myClass = new MyClass();
container.inject(myClass);

print(myClass.version);  // will output -> 1.0

// second way is to directly inject into constructor, this way is better in case that the class will use dependencies inside constructor
container.injectIntoConstructor(MyClass);

const myClass = new MyClass();
print(myClass.version);  // will output -> 1.0

// also you can register factory method
type Car = { name: string };
container.registerFactory<Car>(() => { name: "best car" });

// you can add or set default resolver, so you can modify dependency injection logic in case dependency isn't registered
container.setDefaultResolver((dependency) => {
	return "1";
});

container.setDefaultResolver((dependency) => {
	return "2";
});  // will replace previous default resolver

container.insertDefaultResolver((dependency) => {
	return undefined;
});  // this will not replace previous default resolver and if your default resolver returns undefined it will give a try for previous resolver

work with flamework

// in default mode container will not inject flamework dependencies
// so you need to manually enable it
container.enableFlameworkResolver();  // this will set default resolver

// you can inject into services and components using this method
// notice that you need to do that before ignite
Flamework.addPath("src/shared");
Flamework.addPath("src/server");

container.injectIntoFlamework();

Flamework.ignite();