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

zero-to-one-view

v1.0.0

Published

[![NPM version][npm-image]][npm-url] [![build status][travis-image]][travis-url] [![Test coverage][codecov-image]][codecov-url] [![David deps][david-image]][david-url] [![Known Vulnerabilities][snyk-image]][snyk-url] [![npm download][download-image]][down

Downloads

3

Readme

egg-view

NPM version build status Test coverage David deps Known Vulnerabilities npm download

Base view plugin for egg

it's a plugin that has been built-in for egg.

Install

$ npm i egg-view --save

Usage

// {app_root}/config/plugin.js
exports.view = {
  enable: true,
  package: 'egg-view',
};

Use a template engine

egg-view don't have build-in view engine, So you should choose a template engine like ejs, and install egg-view-ejs plugin.

You can choose a template engine first, link ejs, so we use egg-view-ejs plugin.

egg-view is in eggjs, so you just need configure egg-view-ejs.

// config/plugin.js
exports.ejs = {
  enable: true,
  package: 'egg-view-ejs',
};

Configure the mapping, the file with .ejs extension will be rendered by ejs.

// config/config.default.js
exports.view = {
  mapping: {
    '.ejs': 'ejs',
  },
};

In controller, you can call ctx.render.

module.exports = app => {
  return class UserController extends app.Controller {
    * list() {
      const { ctx } = this;
      yield ctx.render('user.ejs');
    }
  };
};

If you call ctx.renderString, you should specify viewEngine in viewOptions.

module.exports = app => {
  return class UserController extends app.Controller {
    * list() {
      const { ctx } = this;
      ctx.body = yield ctx.renderString('<%= user %>', { user: 'popomore' }, {
        viewEngine: 'ejs',
      });
    }
  };
};

Use multiple view engine

egg-view support multiple view engine, so you can use more than one template engine in one application.

If you want add another template engine like nunjucks, then you can add egg-view-nunjucks plugin.

Configure the plugin and mapping

// config/config.default.js
exports.view = {
  mapping: {
    '.ejs': 'ejs',
    '.nj': 'nunjucks',
  },
};

You can simply render the file with .nj extension.

yield ctx.render('user.nj');

How to write a view plugin

You can use egg-view' API to register a plugin.

View engine

Create a view engine class first, and implement render and renderString, if the template engine don't support, just throw an error. The view engine is context level, so it receive ctx in constructor.

// lib/view.js
module.exports = class MyView {
  constructor(ctx) {
    // do some initialize
    // get the plugin config from `ctx.app.config`
  }

  * render(fullpath, locals) {
    return myengine.render(fullpath, locals);
  }

  * renderString() { throw new Error('not implement'); }
};

render and renderString support generator function, async function, or normal function return a promise.

If the template engine only support callback, you can wrap it by Promise.

class MyView {
  render(fullpath, locals) {
    return new Promise((resolve, reject) => {
      myengine.render(fullpath, locals, (err, result) => {
        if (err) {
          reject(err);
        } else {
          resolve(result);
        }
      });
    });
  }
};

These methods receive three arguments, renderString will pass tpl as the first argument instead of name in render.

render(name, locals, viewOptions)

  • name: the file path that can resolve from root (app/view by default)
  • locals: data used by template
  • viewOptions: the view options for each render, it can override the view default config in config/config.default.js. Plugin should implement it if it has config. When you implement view engine, you will receive this options from render, the options contain:
    • root: egg-view will resolve the name to full path, but seperating root and name in viewOptions.
    • name: the original name when call render

renderString(tpl, locals, viewOptions)

  • tpl: the template string instead of the file, using in renderString
  • locals: same as render
  • viewOptions: same as render

Register

After define a view engine, you can register it.

// app.js
module.exports = app => {
  app.view.use('myName', require('./lib/view'));
};

You can define a view engine name, normally it's a template name.

Configure

Define plugin name and depend on egg-view

{
  "eggPlugin": {
    "name": "myName",
    "dependencies": [ "view" ]
  }
}

Set default config in config/config.default.js, the name is equals to plugin name.

exports.myName = {},

See some examples

Configuration

Root

Root is ${baseDir}/app/view by default, but you can define multiple directory, seperated by ,. egg-view will find a file from all root directories.

module.exports = appInfo => {
  const baseDir = appInfo.baseDir;
  return {
    view: {
      root: `${baseDir}/app/view,${baseDir}/app/view2`
    }
  }
}

defaultExtension

When render a file, you should specify a extension that let egg-view know whitch engine you want to use. However you can define defaultExtension without write the extension.

// config/config.default.js
exports.view = {
  defaultExtension: '.html',
};

// controller
module.exports = app => {
  return class UserController extends app.Controller {
    * list() {
      const { ctx } = this;
      // render user.html
      yield ctx.render('user');
    }
  };
};

viewEngine and defaultViewEngine

If you are using renderString, you should specify viewEngine in view config, see example above.

However, you can define defaultViewEngine without set each time.

// config/config.default.js
exports.view = {
  defaultViewEngine: 'ejs',
};

see config/config.default.js for more detail.

Questions & Suggestions

Please open an issue here.

License

MIT