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

egg-views

v1.0.2

Published

egg view plugin for all templating engines in consolidate, like koa-views

Downloads

6

Readme

egg-views

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

Egg view plugin which is similar to koa-views, supports many templating engines.

Install

egg-views is using consolidate under the hood.

NOTE: you must still install the engine you wish to use, add it to your package.json dependencies.

$ npm i egg-views --save

# Add one of the following:
$ npm i ejs --save
$ npm i vash --save
...

List of supported engines

Usage

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

// if you choose ejs and use .ejs for extension
// {app_root}/config/config.default.js
exports.view = {
  defaultViewEngine: 'views',
  mapping: {
    '.ejs': 'views',
  },
};

// if you choose vash and use .vash for extension
// {app_root}/config/config.default.js
exports.view = {
  defaultViewEngine: 'views',
  mapping: {
    '.vash': 'views',
  },
};

// if you choose vash and use both .html and .vash for extension
// {app_root}/config/config.default.js
exports.view = {
  defaultViewEngine: 'views',
  mapping: {
    '.html': 'views',
    '.vash': 'views',
  },
};

Configuration

Write configurations of the engine you choose to the options.

WARNING: be aware that your code could break if we add an option with the same name as one of your data object's properties. See Conflict.

If you choose to use ejs:

// {app_root}/config/config.default.js
exports.views = {
  engine: 'ejs',
  // ejs config
  options: {
    cache: true,
    debug: false,
    compileDebug: true,
    delimiter: null,
    strict: false,
  },
};

Or choose to use vash:

// {app_root}/config/config.default.js
exports.views = {
  engine: 'vash',
  // vash config
  options: {
    useWith: true,
  },
};

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

Render

There are three default render functions in egg, while the last one is not supported in egg-views.

  • ✔︎ render(name, locals) renders template file, and set the value to ctx.body.

  • ✔︎ renderView(name, locals) renders template file, returns the result and don't set the value to any variable.

  • renderString(tpl, locals) not supported.

Conflict

Unfortunately, due to the using of egg and consolidate, some occupied names can't be used as your data object's properties:

  • ctx
  • gettext
  • helper
  • request
  • locals
  • name
  • root

You should also avoid using the names in configuration options list of the choosing templating engine. Because, if you use these names as your data object's properties, your data will be used as options to build a template firstly, then as the data to construct the final page. For example, if you choose ejs, you should be cautious to use cache filename scope debug ....

Questions & Suggestions

Please open an issue here.

License

MIT