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

@warp-works/studio

v1.0.0-rc12

Published

Cross-domain code generation framework for Rapid Application Development

Downloads

20

Readme

WarpWorks

Cross-domain code generation framework for Rapid Application Development

Overwriting defaults

Overwrite WarpWorks Studio defaults with .warp-works-studiorc:

{
  "port": 3000
}

You can also overwrite WarpWorks Core default with .warp-works-corerc:

{
  "cartridgePath": "../warpjs",
  "outputPath": "../warpjs",
  "projectPath": "../w2projects"
}

This file will be read by the @quoin/node-rc library.

Debug

You can run in debug mode by defining:

DEBUG=W2:Studio:*

Using inside of another project

npm install --save https://github.com/dslama/WarpWorks.git

In your application (server/app.js):

const warpJs = require('@warp-works/warpjs');
const warpStudio = require('@warp-works/studio');

const PATH_TO_ADMIN = '/admin';
app.use(PATH_TO_ADMIN,
    session.middlewares.requiresUser,
    warpJs.middlewares.canAccessAsAdmin.bind(null, 'someUserProp'),
    session.middlewares.unauthorized,
    // application
    warpStudio(PATH_TO_ADMIN)
);

Implementations of session.middlewares.requiresUser and session.middlewares.unauthorized are left as an exercise.

function requiresUser(req, res, next) {
    req.someUserProp = { object };
}

function unauthorized(error, req, res, next) {
    // redirect because cannot access.
}

This implementation for authorization might need to be revised because it should not be limited to WarpWorks users, but should be linked to the hosting app users.

Refer to WarpJS for more details.