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

salak-view

v1.0.2

Published

salak view

Downloads

4

Readme

salak-view

NPM version build status Test coverage David deps NPM download

View for SalakJS 2.0, support for multiple view engine, using consolidate under the hood.

Install

$ npm install --save salak-view

Supported Template Engines

If you want to use ejs engine, You need install ejs.

$ npm install --save ejs

Usage

Config

In plugin:

module.exports = {
  plugin: [
    {
      name: 'view',
      package: 'salak-view'
    }
  ],
  view: {
    dirname: 'view',
    extension: 'html',
    engine: '',
    cache: true,
    map: null,
    config: {}
  }
}

Use in Context or Controller

user/controller/login.js

const { Controller } = require('salak')

class Login extends Controller {
  async actionIndex () {
    await this.render('login')
  }
}

module.exports = Login

API

Options

  • dirname {String} directory for storing views, default view
  • extension {String} template file extension, default html
  • engine {String} Engine for parse file, default ``
  • cache {Boolean} Cache things for reading the file content, default app.env === 'production'
  • map {Object} map a file extension to an engine, like { html: 'ejs' }, default null
  • config {Object} pass to view engine, default {}

Controller.prototype.render(viewName, locals, module)

The function which register on or

  • name {String} view filename
  • locals {Object} variables for view
  • module {String} the view located in, default: the current module

@return will set view html to response.body

context.render(), but module default app.root

Controller.prototype.renderView(viewName, locals, module)

params is the same as Controller.prototype.renderView

@return complied html string,if file ext is html and !options.engine && !map, will return fs.createReadStrem(file)

context.renderView(), but module default app.root

License

MIT