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

controllerim

v3.0.5

Published

A simple, clean and well structured state management library for react

Downloads

20

Readme

Controllerim

A simple, clean and well structured state management library for react

npm version

Installation

npm install controllerim --save

Migrating from Controllerim v2 to v3

The migration process should be very easy. Follow the docs and the example project for understanding the new API.

Basic usage example

Inside ParentController.js:

import { controller } from 'controllerim';

class _ParentController {
  constructor() {
    this.state = {
      message: 'hello' 
    };
  }
  getMessage() {
    return this.state.message;
  }
  setMessage(value) {
    this.state.message = value;
  }
}

export const ParentController = controller(_ParentController);

Inside Parent.jsx:

import React, { Component } from 'react';
import { observer } from 'controllerim';
import { ParentController } from './ParentController';

class Parent extends Component {
  constructor(props) {
    super(props);
    this.controller = ComponentController.create(); //returns a fresh controller instance
  }

  render() {
    return (
      <div>
        <h1>{this.controller.getMessage()}</h1>
        <Child/>
        <button onClick={() => this.controller.setMessage('hello world!')}>Click me to change message</button>
      </div>
    );
  }
};

export default observer(Parent);

Inside Child.jsx:

import React, { Component } from 'react';
import { observer} from 'controllerim';
import {ParentController} from './ParentController'

class Child extends Component {
  constructor(props){
    super(props);
    this.parentController = ParentController.getInstance(); //returns an existing instance of the parentController. You could supply an id if you you have more than one instances of the parent controller.
  }
 
  render() {
    return (
      <div>
        <span>This is a message from parent: {this.parentController.getMessage()}</span>
      </div>
    );
  }
};

export default observer(Child);

Example project

Here is a Simple example project You can see the source code under the example folder: demo-app/src If you want to run it locally: After cloning the repository, navigate to the demo-app folder and type in your terminal:

npm install
npm start

How

Controllerim utilizes Mobx behind the scenes. You don't need to learn Mobx in order to use Controllerim, but a basic understanding of Mobx is recommended.

Api

controller(controllerClass)

Arguments:
  • controllerClass: any es6 class with a state member.
Returns:
  • Object: { create(), getInstance() }: an object with two factory methods for getting a new controller instance

A controller is a plain Javascript class that holds a state and methods for manipulating the state. All the methods of the controller are smartly memoized and computed, thus if you do some heavy calculation, it will be re-calculated when really needed.

The observers (React Components that you wrapped within observer) will react to any change in the state, even changes of deep nested properties.

create(id?: string (default: 'globalInstance') ):

Returns a new instance of the given controller. You should use this method when you know for sure that you need a fresh instance and not an existing one (most of the time you should prefer create over getInstance). You can pass an id, for being used later by getInstance.

getInstance(id?: string (default: 'globalInstance')):

Returns an existing instance of the given controller, or a new one if there isn't any existing instance yet. If you don't supply an id, the return value will be the default global instance.

controller Usage example:

import {controller} from 'controllerim';

class _AppController {
  constructor() {
    this.state = {totalNotesCount: 2};                                 
  }

  getTotalNotesCount() {
    return this.state.totalNotesCount;
  }

  increaseCounter() {
    this.state.totalNotesCount++;
  }
}

export const AppController = controller(_AppController);

Your React component will create an instance of the controller like this:

import {AppController} from 'controllerim';

class App extends React.Component {
  constructor(props) {
    super(props);
    this.controller = AppController.create();
  }

  render(){
    <div>
      <div>{this.controller.getTotalNotesCount()}</div>
      <div onPress={() => this.controller.increaseCounter()}>click me</div>
    </div>
  }
}

useController(controllerInstance)

Allows you to use controller inside a functional component. Note that you still have to wrap your functional component within observer.

import React from 'react';
import {observer, useController} from 'controllerim';
import {FunctionalComponentController} from './TestComponentController';

export const FunctionalComponent = observer(() => {
  const controller = useController(FunctionalComponentController.create());
  return (
    <div>
      <div>{controller.getUserName()}</div>
      <div onClick={() => controller.changeUserName()}>click me</div>
    </div>
  );
});

observer(ReactComponent)

To become reactive, every React component that uses a controller, should be wrapped within observer.

import {observer} from 'controllerim';

export const SomeSmartComponent = observer(class extends React.Component {
...
})

store(storeClass)

A store is just a global singleton controller that is not conceptually bound to any specific component.

inside AppStore.js:

  import {store} from 'controllerim';

  class _AppStore {
    constructor(){
      this.state = {useName: 'bla'};
    }

    getUserName() {
      return this.state.userName;
    }
  }

  export const AppStore = store(_AppStore);

Inside component.jsx:

import React from 'react';
import {observer} from 'controllerim'
import {AppStore} from './AppStore';

class SomeComponent extends React.Component {
  render(){
    <div>{AppStore.getUserName()}</div> // <== The component will re-render on any change in getUserName
  }
}

export default observer(SomeComponent);