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

pkframe

v0.8.5

Published

Client for pkframwork | Instal, webtest, auto refresh, typescript compile

Downloads

3

Readme

PK Frameword :: Client

Client for pkframwork | install, server, liveload, typescript whatch...

First of all: Sorry for my shitty english...

Here are just client tool usage. To learn more about framework: Quick Start Guide

Installation

First, install Node.js. Then, install the latest pkframe cli command-line tools in your terminal.

$ npm install -g pkframe

Usage

init

The init command will download a startup template for your project. Basically this client will download one of the pkframework-examples as the initial template and dependences for you.

$ pkframe init

Options

These are keys in the options object you can pass

  • -p [pkg-name] example he will use as the initial template [default=basic]

You can see anothers 'templates' here. Just follow folders name.

go

This is where the magic happens.

$ pkframe go

This command does many things:

  • Starts a web-server to test your game
  • Compile(and watch modifications) typescript code and deploy
  • Start your browse with liverload. Auto update whenever the code is updated

This command expects to find an [index.html], where you will start your browser with liveload. Typescript compiler will watch for .ts files modifications except for the [assets, node_modules, vendor] folders and will deploy them to [dist / js / app.js].

{
    "compilerOptions": {
        "module": "amd",
        "target": "es5",
        "sourceMap": true,
        "outFile": "dist/js/app.js"
    },
    "exclude": [
        "assets",
        "node_modules",
        "vendor"
    ]
}

This can be configured in the tsconfig.json file itself. All initial models already come with a tsconfig.json preconfiguration. You can change if you want.

install

Here it will download / install the dependencies listed in the configuration file [pkconfig.json]. Things like assests pack, ts and js lib.

$ pkframe install

If there is no configuration file, it will create a default.

{
    "install": {
        "assets": {
            "url": "https://github.com/pe77/pkframework-assets/archive/master.zip",
            "folder": "assets"
        },
        "dependencies": {
            "pkframework": {
                "url": "https://github.com/pe77/pkframework/archive/master.zip",
                "use": "build/"
            }
        }
    }
}

You do not have to worry about this command unless you wanted to create a package / template. It is automatically used when you use pkframe init