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

@mreinlaender/i-inject

v1.0.4

Published

Small DI-Container for typescript based frontend applications. Contains scope handling for automation via routes

Downloads

81

Readme

i-inject

A multi-scope singleton injection-container intended for use in a Routed SPA, written in TypeScript.

  • Lazy initialization of instances
  • Automaticly drops stored instances if the scope changes to something they weren't intended for

Usage

test-store.ts

class TestStore {
    public static typeName = "TestStore";

    // your code here
    ...
}

inject.register(TestStore, '/test/*', 'anther/route/:id/test', '/something/differen/test');

test-component.ts

const TestComponent = () => {
    const { myList, onAddNewItem } = inject.get(TestStore)

    const displayList = myList.map(iten => <div>{item}</div>);

    return (
        <div>
            {displayList}
            <button onClick={onAddNewItem}>Add New</button>
        </div>
    );
}

Use the wildcard '*' to permit everything further "down" the current scope.

Example:

inject.register(TestStore, '/test/*');

Will be accessible in /test/anything/goes and /test/13asd213-12asd1-11as1d3-a2s1d312asd/even/this

A convenience export const ALLWAYS_ACTIVE = '*' is provided

leading to

inject.register(TestStore, ALLWAYS_ACTIVE)

IDs

The :id placeholder supports Numbers and UUID-4 by default. Custom patterns can be registered with addIdPredicate

SETUP

You can leave and enter scopes manually, but aside from specific cases (e.g. opening a modal /wizard) it's not advised.

To keep the current-scope in line with the url use the changeTo-function and add something like the following to the initialization part of you application.

// The following code assumes you are using a Hash-Router
// If this is not the case, don't use the `window.location.hash` leveraged below

const sanitize = (arg: string) => arg.substring(1).split("&")[0];

const beforeLocationChange = new CustomEvent("pushstate", {
  detail: {},
  bubbles: true,
  cancelable: true,
  composed: false,
});

const pushState = history.pushState;
history.pushState = function () {
  pushState.apply(
    history,
    arguments as unknown as [
      data: any,
      unused: string,
      url?: string | URL | null | undefined
    ]
  );
  window.dispatchEvent(beforeLocationChange);
};

window.addEventListener("pushstate", () => {
  inject.changeTo(sanitize(window.location.hash));
});

window.addEventListener("popstate", () => {
  inject.changeTo(sanitize(window.location.hash));
});

// enter initial scope (also enables deep reloads)
inject.enter(sanitize(window.location.hash));

If you are wondering about the CustomEvent, the history.pushState function does currently not trigger an event on its own.

And you are done - Enjoy accessing singleton instances from where you want, and only from there.

Instances and contained data will be dropped after a change to the current-scope, providing a particularly safe / clean working environment.

inject.register(Test, '/test/:id', '/something/differen/test')
inject.enter('/test/123');

expect(inject.get(Test)).toBeDefined();

inject.changeTo('/wont/be/active);

expect(inject.get(Test)).toBeUndefined();