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

@cherrypulp/dependency-injector

v0.0.8

Published

A basic and simple dependency injector with no dependencies.

Downloads

10

Readme

DependencyInjector

codebeat badge Issues License npm version

A basic and simple dependency injector with no dependencies.

Why use dependency injection?

You might by now be thinking "hey that's pretty cool, but why would I do that?". There's a couple reasons why you might want to use dependency injection in VueJS

Testability

Imagine you're writing an application that makes calls to an API, you're probably using a package for making those HTTP requests. However, when you're running your unit tests you'd probably rather not have those tests run wild and create 200 users in your API. Using dependency injection you could just swap out the binding for your HTTP service with a dummy service (that could for example assert the required calls are made), without having to change a single line of code.

Example

import axios from 'axios';

deps.singleton('$http', axios);

Then for your unit tests

deps.singleton('$http', DummyHttpService);

Explicit dependencies

TODO

Easier refactoring

TODO

Installation

Installing using npm install @cherrypulp/dependency-injector?

WARNING Look at this before building for production.

Quick start

Vanilla

import DependencyInjector from '@cherrypulp/dependency-injector';

const deps = new DependencyInjector();

deps.constant('foo', 'BAR');
deps.register('bar', (key) => key);
deps.singleton('api', ApiService);

// then

deps.resolve('foo'); // return 'BAR'
deps.resolve('bar')('ok'); // return 'ok'
deps.resolve('api'); // return Api service

Resolve parameters

function func(foo, api) {
    /* ... */
}

const params = deps.parameters(func); // return ['BAR', ApiService]

Patch method

WARNING Look at this before building for production.

const func = deps.patch(function (foo, api) {
    // foo === 'BAR'
    // api === ApiService
});

VueJS

import VueDependencyInjector from 'dependency-injector/vue-dependency-injector';

const options = {
    constants: {
        foo: 'BAR',
    },
    factories: {
        bar: (key) => { ... },
    },
    services: {
        api: Api,
    },
};

Vue.use(VueDependencyInjector, options);

// or

new Vue({
    el: '#app',
    ...options,
});

// then

this.$dependency.constant('foo'); // return 'BAR';
this.$dependency.factory('bar')(key); // use bar factory
this.$dependency.service('api'); // return Api service;

TODO

Mangling

When building for production you'll most likely minify your code. Most minifiers employ a technique called "name mangling" which poses a couple problems with this library if you use method injection. You can read more about this here.

In short, you'll need to ensure your minifier won't mangle the parameter names of your services, for UglifyJS (default for webpack) this can be done like this:

new webpack.optimize.UglifyJsPlugin({
    compress: {
        warnings: false
    },
    sourceMap: true,
    mangle: {
        except: ['Service'], // blacklist your services from being mangled
    },
});

Versioning

Versioned using SemVer.

Contribution

Please raise an issue if you find any. Pull requests are welcome!

Author

License

This project is licensed under the MIT License - see the LICENSE file for details.

TODOS

  • [ ] Documentation
  • [ ] VueX integration
  • [ ] Unit tests
  • [x] use Map instead of Object for $$dependencies
  • [x] ability to freeze values
  • [x] ability to cache values