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

@appolo/view

v8.0.2

Published

appolo view module

Downloads

52

Readme

appolo view module

Installation

the view engine must be installed in package.json in the example npm i nunjucks.

npm i @appolo/view
npm i nunjucks

Options

| key | Description | Type | Default | --- | --- | --- | --- | | viewFolder | view folder to search the view paths | string| views| | viewCache | cache the compiled views | boolean | true | | viewExt | views files extension | string | html | | viewEngine | the view engine to be used from list| string | nunjucks | | maxPathCache | max number of cached view paths | number | 1000 |

in config/modules/all.ts

import {App} from 'appolo';
import {ViewModule,ViewEngines} from '@appolo/view';

export = async function (app:App) {

    await app.module(new ViewModule({
        viewEngine:ViewEngines.nunjucks
    });
}

Usage

now you can use the res.render function in the controller

import {controller, inject, IResponse, get, StaticController} from 'appolo';

@controller()
export class ViewController extends StaticController {

    @get("/test/view")
    async someView(req, res: IResponse, route) {
        await res.render("path to view", {test: req.query.test}
    }
}

if the path is not defined the view will be searched in the same folder as the controller and file name as the action in the example below it will search for view2.html

import {controller, inject, IResponse, get, StaticController} from 'appolo';

@controller()
export class ViewController extends StaticController {

    @get("/test/view2")
    async view2(req, res: IResponse, route) {
        await res.render( {test: req.query.test}
    }
}

the view can be rendered with view decorator

import {controller, inject, IResponse, get, StaticController} from 'appolo';
import {view} from '@appolo/view';


@controller()
export class ViewController extends StaticController {

    @get("/test/view2")
    @view("some path")
    view(req, res: IResponse, route) {
       return {test: req.query.test}
    }
}

promises also supported

import {controller, inject, IResponse, get, StaticController} from 'appolo';
import {view} from '@appolo/view';

@controller()
export class ViewController extends StaticController {

    @get("/test/view2")
    @view()
    async view(req, res: IResponse, route) {
       let result  = await doSomeThingAsync();
       return result
    }
}