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 🙏

© 2025 – Pkg Stats / Ryan Hefner

neuro-react-server

v0.1.1

Published

React build to send into electron and another application with update semantic

Readme

neuro-react-server

React build to send into electron and another application with update semantic

Build: npx tsc or tsc (if typescript installed globaly) Publish: npm run build:publish

Usage

Init frontend server:

const FrontServer = require("neuro-react-server")
const http = requrie("http")
const path = rqeuire("path")

const simpleRequestListener = (req, res) => {
  res.writeHead(200)
  res.end("Hi!")
}

const server = http.createServer(simpleRequestListener) // you can use express.js or other frameworks to create the server
const frontendServer = new FrontServer({
  server: server,
  ClientSrc: path.resolve(__dirname, "frontend"), // Frontend src
  production: false, // use react.production.min.js or react.development.js (default: false)
  addReact: false // Add react engine on component (default: fasle)
}

server.listen(3000) // listen on 3000 port

Project struct:

index.js
frontend
|> component
|> |> index.jsx
|> clock
|> |> arrow
|> |> |> index.jsx
|> |> clockFace
|> |> |> index.jsx

WARNING!!

component - is folder div for render - path to folder (example: ReactDOM.render(Arrow(), document.getElementById("/clock/arrow"))) main function to render - name of component

JSX File struct:

// Path: frontend/clock/arrow/index.jsx
const Arrow = () => (
  <h1>Hi!</h1>
)

ReactDOM.render(Arrow(), "/clock/arrow")

addComponent function - add component to project. Example:

// index.js
...
const id = "number one components" // A group of components have the same id 
frontendServer.addComponent("/component", id)
// frontend/component/index.jsx
const Component = () => (
  <h1>Hi!</h1>
)

ReactDOM.render(Component(), document.getElementById("/component"))

update function - update all components Example:

// index.js
frontendServer.update() 

getComponentById and getComponentsById functions - get component or components by id Example:

// index.js
frontendServer.getComponentById("number one components", "/component") // return frontend/compontent/index.jsx body and other data
frontendServer.getComponentsById("number one components") // return all components, who have same id