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

livelykernel

v2.1.2

Published

Core modules of the Lively Kernel

Downloads

6

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

robertkrahnrobertkrahnlauritzthamsenlauritzthamsen

Keywords

Readme

Lively Kernel

Lively Kernel is a web-based runtime and development environment that makes creation of web applications much more immediate and direct. Please see lively-kernel.org for more general information about the Lively Kernel project.

For feedback, announcement and discussions, please feel invited to subscribe to our mailing list.

This repository is a fork of the Lively Kernel Webwerkstatt wiki at HPI. To learn more about the motivation and long-term vision for this repository see the wiki.

Installation

Get Lively Kernel core up and running.

Prerequisites

  1. node.js: In a terminal try running node -v. If that fails install node.js.

  2. npm: Try running npm -v. If that fails run curl http://npmjs.org/install.sh | sh in your terminal to install it.

Running Lively

  1. Clone the Lively Kernel repository.
git clone [email protected]:rksm/LivelyKernel.git ~/LivelyKernel
  1. Go into the Lively Kernel directory and run npm:
cd ~/LivelyKernel
npm install
  1. In that directory start the minimal server
lk server

That's it. You can now visit a rather boring page blank.xhtml workd or run the tests with lk test.

Setup an apache server

Note 1 You only need to do this if you want to run a full-fletched Lively Kernel installation that provides the functionality to run a Lively Wiki.

Note 2 We are currently working on a pure node.js solution to get rid of apache and the complicated setup process.

See installation notes for apache on Debian and Mac OS x for details.

Installing the Webwerkstatt PartsBin

You can install all the cool tools from Webwerkstatt's PartsBin. Have a look at the HOWTO.

Running the tests

Command line tests

Note: Make sure you have all required node.js modules installed. Run npm install to do so. To start the Lively tests from the command line first start the server:

lk server

To initiate a test run do

lk test

This runs tests in the browser you specified in testing/config.js. See lk test --help for all the test runner options.

LivelyKernel on Travis-CI

We use Travis-CI to run tests continuously on every commit into the Master branch: Build Status

Contributing

Please this wiki page for some best practices to work with git and github.