mini-store - GitLite

KO | EN

gitlite — search

#python #typescript #android #machine-learning #rust #linux #docker #nodejs #macos #windows #pytorch #mcp #ios #openai

mini-store

(★ 100)

A minimal state store for React component.

파일 탐색기

최종 버전 다운로드 (.zip)

- - connect.test.tsx
  - create.test.tsx
  - Provider.test.tsx
- connect.tsx
- create.ts
- index.ts
- Provider.tsx
- types.tsx
.gitignore
.prettier
.travis.yml
CHANGELOG.md
commitlint.config.js
jest.config.js
package.json
README.md
setup.js
tsconfig.json

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/yesmeck/mini-store

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd mini-store

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Node.js

쉬움 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Node.js npm 명령어를 쓰려면 Node.js가 설치되어 있어야 합니다. LTS(장기지원) 버전을 추천합니다.

npm install

package.json에 명시된 라이브러리들을 내려받아 설치합니다.

npm start

개발/실행 서버를 켭니다.

✅ 명령어 실행 후 터미널에 나타나는 주소(보통 http://localhost:3000 형태)를 브라우저에서 열어보세요.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# mini-store

**Deprecated, see [use-context-selector](https://github.com/dai-shi/use-context-selector) for optimized state subscribtion**

[![Travis](https://img.shields.io/travis/yesmeck/mini-store.svg?style=flat-square)](https://travis-ci.org/yesmeck/mini-store)

A state store for React component.

## Motivation

When you want to share a component's state to another one, a commom pattern in React world is [lifting state up](https://reactjs.org/docs/lifting-state-up.html#lifting-state-up). But one problem of this pattern is performance, assume we have a component in following hierarchy:

```javascript
<Parent>
  <ChildA />
  <ChildB />
  <ChildC />
</Parent>
```

`ChildA` want to share state with `ChildB`, so you lifting `ChildA`'s state up to `Parent`. Now, when `ChildA`'s state changes, the whole `Parent` will rerender, includes `ChildC` which should not happen.

Redux do a good job at this situation throgh keeping all state in store, then component can subscribe state's changes, and only connected components will rerender. But `redux` + `react-redux` is overkill when you are writing a component library. So I wrote this little library, It's like Redux's store without "reducer" and "dispatch".

## Example

[See this demo online.](https://codesandbox.io/s/mq6223x08p)

```javascript
import { Provider, create, connect } from 'mini-store';

class Counter extends React.Component {
  constructor(props) {
    super(props);

this.store = create({
      count: 0,
    });
  }

render() {
    return (
      <Provider store={this.store}>
        <div>
          <Buttons />
          <Result />
        </div>
      </Provider>
    )
  }
}

@connect()
class Buttons extends React.Component {
  handleClick = (step) => () => {
    const { store } = this.props;
    const { count } = store.getState();
    store.setState({ count: count + step });
  }

render() {
    return (
      <div>
        <button onClick={this.handleClick(1)}>+</button>
        <button onClick={this.handleClick(-1)}>-</button>
      </div>
    );
  }
}

@connect((state) => ({ count: state.count }))
class Result extends React.Component {
  render() {
    return (
      <div>{this.props.count}</div>
    );
  };
}
```

## API

### `create(initialState)`

Creates a store that holds the state. `initialState` is plain object.

### `<Provider store>`

Makes the store available to the connect() calls in the component hierarchy below.

### `connect(mapStateToProps)`

Connects a React component to the store. It works like Redux's `connect`, but only accept `mapStateToProps`. The connected component also receive `store` as a prop, you can call `setState` directly on store.

## License

MIT