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

reactatron

v0.0.3

Published

React stuff

Downloads

2

Readme

Reactatron

Known Unknowns

  • Do we need to shove children into props for every component?

TODO

thoughs

  • React but with the functions (AKA factory) way
  • built for coffee script (maybe ES6?)
  • has a flux-like event based system
  • has a key,value store persisted in localStorage as json
  • has a dead simple data binding system
  • provide a super api for making components
  • provide subclassing components
  • eveything is built as modules with the borders well documented
  • module: js css framework (need benchmarking)
  • we provide the start and stop level boilerplate code
  • maybe we prevent components from being defined dynanically because we know start/stop state

Arcitecture

component

  • A Reactatron Components is any function that returns a React Element
  • Reactatron/DOM is every React.DOM element in function (React.createFactory) form
Questions:
  • If you pass children in as arguments to a React Component props.children is ignored
  • How do we make ReactElement.createElement(child.type, newProps) work with functions?

Styled Component

A Styled Component is a wrapper that merges the given style prop the style object given at component definition time

{div} = require 'reactatron/DOM'

module.exports = div.withStyle 'RedBox',
  borderColor: 'red'

App

  • starts and stops the global listeners like popstate
  • initializes the state of the app
  • do we need some sort of "plugin" system here? NO!!!

State

  • state is just a big plan object

  • IT IS NOT state a string key, value store !!!!!

  • this is given to the page component

    • which should pull the data it needs and also register a handler
  • all of its top level values are available

  • um... stores state?

  • lets you know when state changes

  • lets you ask for the values of keys and get the current valye and updates, via callback and imediate return


keys = [
  'current_user.first_name',
  'current_user.last_name',
]

state.get keys, (values) ->
  {first_name, last_name} = values
  # or better yet
  @setState(values)


component 'FilesPage',

  getInitialState: ->
    data = App.tellMeWhenChange(

    )
    @setState(data)

  render: ->
    {first_name, last_name} = App.state.current_user
    h1(null, "Welcome back #{first_name} #{last_name}")



The Cycle

First render

render: ->

  DataQuery
    keys:
      'current_user.first_name'
      'current_user.last_name'
    loading: ->

    loaded: (values) ->

    error: (error) ->



DataQuery = component
  propTypes:
    keys: queryKeySet



  render: ->

React Tree

Actions

ReactatronApp = require('reactatron/App')
App = new ReactatronApp

App.router.map ->
  @match '/', @redirectTo '/transfers'

App.start()
App.stop()

@context.path
@context.params
@context.setPath(path)
@context.setParams(params)
@context.setLocation(path, params)

App.on 'location:change',  @onLocationChange
App.off 'location:change', @onLocationChange
App.routes ->
  @match

Button = require('components/Button')
App.component 'MagicButton',
  render: ->
    Button()

There needs to be an internal way, other than the app the user create, to set the location or not create apps?

Components

  • Text

No text is selectable unless wrapped in one of these text components

  • ColumnsContainer
  • RowsContainer
  • Button
  • Link

Documentation

?? https://github.com/coffeedoc/codo ??