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

weex-x

v0.1.2

Published

Flux-inspired-Architecture-Vuex-inspired-Architecture for Weex.

Downloads

5

Readme

Weex-x

Flux-inspired-Architecture-Vuex-inspired-Architecture for Weex.

note: this repo only works well with Weex JS Framework v0.16.x and higher.

Install

npm install weex-x

Usage

First you need to create a new Store with some options.

  • state: the real JSON data work in the background.
  • getters: you can define some getters whose value depends on the state.
  • mutations: you can not modify the state directly but can define some mutations to dispatch anytime.
  • actions: you can also define some functions to dispatch those mutations.

For example:

import { Store } in 'weex-x'
const store = new Store({
  state: { firstName: 'Jinjiang', lastName: 'ZHAO' },
  getters: { fullName: state => `${state.firstName} ${state.lastName}` },
  mutations: {
    setFirstName (state, name) {
      state.firstName = name
    },
    setLastName (state, name) {
      state.lastName = name.toUpperCase()
    }
  },
  actions: {
    setFirstName: ({ commit }, payload) => commit('setFirstName', payload),
    setLastName: ({ commit }, payload) => commit('setLastName', payload),
    setFullName({ commit }, payload) {
      const result = payload.split(' ', 2)
      commit('setFirstName', result[0])
      commit('setLastName', result[1])
    }
  }
})

And then just set store to the top Vm options with the store you created and set init to each Vm options. You can access the store by $store in Vms.

import { Store, init } in 'weex-x'
const store = new Store({...})
export {
  store,
  init,
}

If your Vm already has init in its options. You can use it like this:

import { Store, init } in 'weex-x'
const store = new Store({...})
init = init(function () {
  // todo
})
export {
  store,
  init,
}

At last you can quickly define more Vm options with some helpers:

import { Store, init, mapGetters, mapActions } from 'weex-x'
const store = new Store({...})
export {
  store,
  init
}
export const computed = mapGetters([
  'firstName',
  'lastName',
  'fullName'
])
export const methods = mapActions([
  'setFirstName',
  'setLastName',
  'setFullName'
])

Examples

See examples for more.

Contribution

  • npm run build to build generated javascript code to ./dist/
  • npm run dev to watch the ./src/* changes to run the build process
  • npm run test to run test cases
  • in ./examples/ you can npm i && npm run build to build all examples to ./examples/dist/
  • also in ./examples/ you can npm run dev to watch changes of all examples to run the build process