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

focus-center

v3.0.1

Published

focus center

Downloads

15

Readme

react18 is supported now!

focus-center

focus尝试解决的问题:提高业务组件的复用性,让你的团队可以快速的开发或者维护页面的业务逻辑,可以让你的团队把重心放在开发业务组件上。看到这里可能你会有点不明白,作者说的什么东西啊,别急,我会慢慢解释。 现在前端页面的开发早变成了一个个的组件,但是组件应该是和复用性挂钩的,这也是评价一个组件好坏的指标之一。如果业务重复,ui重复,这个时候如果还是在页面写重复的组件,无疑是在浪费工作量,并且据我所知在页面工程上进行组件的维护是一个非常不吃力的做法,并且还会增加整个工程的混乱度,团队还会不停的写着重复的代码。 正确的做法是需要进行业务组件的沉淀,将它从页面工程分离,进行单独的维护,将焦点放在业务组件上,然后再下放到你的页面中。这样做的好处就是可以解放整个团队的生产力。

对于多页应用的使用场景

focus需要结合focus-loader来使用,入口是index.view文件

安装

npm install focus-center focus-loader --save;
// loader 规则从下到上,从右到左,所以focus-loader需要在babel-loader后面
module: {
    rules: [
      {
        test: /\.(js|jsx|tsx)$/,
        use: [{ loader: 'babel-loader' }],
        exclude: /node_modules/,
      },
      {
        test: /\.view$/,
        use: [
          { loader: 'babel-loader' },
          {
            loader: 'focus-loader',
            options: {

            }
          }],
        exclude: /node_modules/,
      },
    ]
  }

tips:一般的你可能会需要配置多个入口文件(src/pageOne/index.view,src/pageTwo/index.view,...)

focus-center快速预览

在你的页面上应该只有三个很重要的文件(index.business,index.model,index.view),正如上面的页面工程结构图所展示的,黑框部分是focus的项目结构,但请忽略common这个公共的组件文件夹,正确的做法是将这个业务组件库分离出去,单独发布。如果你需要使用三方提供的业务组件,这种情况你才能在页面工程下写定制的组件,但是尽量保持页面工程的干净。

  • *.business文件
这个文件是页面工程的业务逻辑文件,如果业务组件开发良好,那么需要写的页面业务逻辑是很少的。在*.business文件中你可以更新对应的组件或者更新整个页面的model。
  • index.model文件

    这个文件输出整个页面的model,需要导出一个单纯的object data。

    export default {
        dataSource:[
            {
                name:'madongmei',
                info:'mashenmemei',
                id:'******',
            }
        ]
    }
  • index.view文件

import React from 'react';
import 'antd/lib/modal/style/css.js';
import MyTodoList from './common/MyTodoList/index.jsx';
import Mydia from './common/MyDialog/index.jsx';
import './index.business';

<View modelFromServerKey="model" customModel="./index.model" root="root">
    <Scope>
        <Text type="h1" value="@model.text" />
        <MyTodoList
            dataSource="@model.dataSource"
            id='myTodoListOne' />
    </Scope>
    <Text type="h2" value="@model.text" />
    {** 如果应用是spa **}
    <Router>
        <Switch>
            <MyTodoList
                exact
                path="/information"
                dataSource="@model.dataSource"
                id='myTodoListRute' />
                {** 404 **}
            <MyTodoList
                dataSource="@model.dataSource"
                id='myTodoListRute404' />
        </Switch>
    </Router>
    <MyTodoList
        dataSource="@model.dataSource"
        id='myTodoList' />
    <Scope>
        <Text type="h3" value="@model.text" />
        <MyTodoList
            dataSource="@model.dataSource"
            id='myTodoListTwo' />
    </Scope>
    <Scope>
        <Text type="h3" value="@model.text" />
        <MyTodoList
            dataSource="@model.list.dataSource"
            id='myTodoListThree' />
    </Scope>
    <Mydia id="myDia" visible="@model.dialogVis"  />
</View>
index.view文件是页面的视图文件,这个文件就是你组织业务组件地方。
为了保持.view文件的干净清爽,index.view文件中有一只能有import语句,和View tag,如果加入了其他的一些语句,则会报错。View tag上有三个prop。modelFromServerKey是从服务端过来的静态data,最后会从index.model文件中导出的model做一个合并。
   window[modelFromServerKey]=window.model={};
   const wholePageModel=Object.assign(customModel,window.model);

一些概念和规范

  • 如果你需要将业务组件的事件通过event center发送出来,比如通过整个model和其他的业务组件通信或者更新model,则必须在你的业务组件中引入focus高阶组件,这个高阶组件会赋予wrapper组件两个props,一个emmit事件的prop,一个changeProps。 emmit第一个参数是事件的type,用来描述事件的行为,第二个参数则是事件传入的参数。给业务组件传入id prop,主要是用来订阅组件的事件。
tips:emmit单词拼写错误,version:2.1.2已经修复,emmit和emit都可以使用,3.x版本将移除emmit
    import {getComponent,updateModel,getModel} from 'focus-center';
    getComponent(componentId).suscribe((eventAction,target)=>{
        target.setProps({},(nextProps)=>{

        });
        switch(action.type){
            case *** :
                updateModel({},(nextModel)=>{

                });
        }
    });
import React from 'react';
import PropTypes from 'prop-types';
import focus,{route} from 'focus-center';
import { Button } from 'antd';
import 'antd/lib/button/style/css.js';
import Action from '../commonMod/action/index.jsx';

//如果你的应用是spa而不是多页应用,则需要使用route hoc
// index.view文件中不需要导入Router和Switch组件
@route
@focus
class MyTodoList extends React.Component {
    static displayName = 'MyTodoList';

    static propTypes = {
        dataSource: PropTypes.arrayOf(PropTypes.shape({
            addr: PropTypes.string,
            info: PropTypes.string,
        }))
    };

    static defaultProps = {
        dataSource: [
            {
                id: 10931234234232,
                addr: 'this is addr',
                info: 'from logic',
            },
            {
                id: 11931234234232,
                addr: 'this is addr',
                info: 'from logic',
            },
            {
                id: 18931234234232,
                addr: 'this is addr',
                info: 'from logic',
            },
        ]
    }
    constructor(props) {
        super(props);
    }

    handleClick = (params) => {
        const { emmit,changeProps} = this.props;
        emmit('CHANGE_SELF', { ...params });
    }
    changeSelfProps = () => {
        const { emmit } = this.props;
        emmit('CHANGE_PROPS');
    }
    render() {
        const { dataSource, emmit } = this.props;
        return (<div>
            <ul>
                {dataSource.map((el) => {
                    return (<li
                        onClick={this.handleClick.bind(this, el)}
                        key={el.id}>
                        <dd>addr:{el.addr}</dd>
                        <dd>info:{el.info}</dd>
                    </li>);
                })}
                <Button
                    onClick={this.changeSelfProps}
                    type="primary">change this com's model</Button>
                <Action emmit={emmit} />
            </ul>
        </div>);
    }
};
export default MyTodoList;

对于单页应用使用的场景(单页应用[email protected],[email protected])

一般的需要在单页中引入redux用来管理整个页面的状态,但是和react-redux不同,focus会和store解耦,不会侵入你的组件,就是react-redux的connect hoc,如果组件和connect结合,那必然是需要用到mapStateToProps,然后右需要去重新定一个组件,一般的这种组件是不可复用的

取而代之的是使用:

import { getComponent, updateModel, getModel } from 'focus-center';
import actions from './store/actions';
   getComponent('testRouteOne').selectStoreStateToProps((storeState) => {
   console.log(storeState, 'storeState');
   return {

   };
}).subscribe((eventAction, target) => {
   /***
    * 
    * api  setProps is invalid if there is a redux store,you sholud use redux store 
    * to manage your whole state
    * 
    * **/
   console.log(eventAction, 'eventAction');
   updateModel((dispatch) => {
       fetch('/xxxx', {
           method: 'POST',
           headers: {
               contentType: 'application/x-www-form-urlencoded',
               xPoweredBy: 'huangtao',
           },
           body: 'name=huangtao&from=hubei',
       }).then((res) => {
           console.log(res, 'res');
           dispatch({
               type: actions.CHANGE_LINK_LIST,
               data: [{
                   name: '商品架构页面',
                   link: '/structure',
                   id: 'goodsStructure'
               }]
           })
           dispatch({
               type: actions.CHANGE_ONE,
               data: {
                   one: 'one',
                   two: 'two',
                   three: 'three',
               }
           })
       }).catch((e) => {

       }).finally(() => {
           // shut down something
       });
   });
});

selectStoreStateToProps是个listener,store的每一次更改,都会触发listener的调用,确保输出到对应组件的store是正确的

单页应用通常需要使用route,你现在可以这样来组织你的spa的view 如果index.model文件导出的是一个store,则modelFromServerKey="model"将不再适用,对于一个使用了redux-store的应用来说,再去暴露这个key不再有意义

import React from 'react';
import TestRoute from './common/TestRoute.jsx';
import SideBar from './common/sideBar';
import FooterBar from './common/footBar';
import './index.business';
import './index.scss';

<View  customModel="./index.model" root="root">
   <Scope className="h-app-container">
       <Scope className="h-side-bar">
           <SideBar id="sideBar" />
       </Scope>
       <Scope className='h-main-body'>
           <Scope>
               <Switch>
                   <RouteScope  path="/one" >
                       <TestRoute childrenPath="/one/three" id="testRouteOne" />
                       <TestRoute childrenPath="/one/two" id="testRouteTwo" />
                   </RouteScope>
                   <RouteScope exact path="/details">
                       <TestRoute id="testRouteThree" />
                       <TestRoute id="testRouteFour" />
                   </RouteScope>
                   <RouteScope exact path="/details/:id">
                       <Text type="div" value="huangweidong" />
                       <TestRoute id="details" />
                   </RouteScope>
                   <RouteScope>
                       <TestRoute id="testRouteFive" />
                   </RouteScope>
               </Switch>
           </Scope>
           <FooterBar />
       </Scope>
   </Scope>
</View>

ReactScope是一个内置的组件,Switch的功能则和react-router-dom一样, 因为需要将match,location,computedMatch...等来自react-router-dom的props注入到ReactScope的子节点中,所以使用了cloneElement来注入props。

同样的focus-center提供了一个route注解,用来注入(link: Link, switch: Switch, route: Route)react-router-dom基础组件,但通常的只有navbar需要这个。

import React from 'react';
import focus, { route } from 'focus-center';
import PropTypes from 'prop-types';

@route
@focus
class SideBar extends React.Component {
    static defaultProps = {
        linkList: []
    };
    static propTypes = {
        linkList: PropTypes.arrayOf(PropTypes.shape({
            link: PropTypes.string.isRequired,
            name: PropTypes.string.isRequired,
            id: PropTypes.string.isRequired,
        }))
    };
    render() {
        const { linkList, link: Link } = this.props;
        return (<div className='h-side-bar-container'>
            <ul>
                {linkList.map((linkEl) => {
                    return (<li key={linkEl.id}>
                        <Link to={linkEl.link}>
                            {linkEl.name}
                        </Link>
                    </li>)
                })}
            </ul>
        </div>)
    }
};

export default SideBar;

对于单页应用很重要的一点是导出的model必须是一个react store 你的index.model文件

import store from './store';

export default store;