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

vacation

v0.2.8-1

Published

build tools for ctrip.com vacation department web front-end group

Downloads

29

Readme

vacation

vacation has two tools, build and server.

learn & use => wiki

server

vacation server now is still beta now, its goal is to be a express-like server for the front ent developers, the first step is serves for the static contents like html,css,javascript etc. and the second step is feed it a server.js file to serves for every dynamic content like a real server.

build

the build tools is designed for the seajs workflow. seajs is like require.js but the different specification called CMD. seajs has a brother called SPM,but the latest version of it is focus on the package manager, not the build tool, so vacation build appeared to resolve the problems, it holps to adapt different directory structure, and got some inspiration from FIS that generate a map.json file that you can get all informations of your source files in this file.


get help information

vacation -h,vacation init -h,vacation server -h, vacation build -h

vacation init -c

initialize a vacation.json file in the current-work-directory.

  1. vacation init -cf force to overwrite a config file if it had exists already.

vacation server start

start a server for the develope purpose and point the www dir to the current dir.

vacation build start

the config file should be provided if you need to use this command.

vacation build tpl

transport templates.

build command have options:

  -h, --help               output usage information
  -m, --map                write the map.json file to the $cmd_cwd dir.
  -c, --concat             concat all modules that the $pkg module dependen-
       cies. config the output file rule in the vacation.json
  -t, --transport <dir>    transport and output the results to the `dir` dir.
       `dir` relative to the $dest dir.
  -o, --optimize           optimize/uglify the modules that transported
       or/and concated results.
  -C, --cssinline          inline dependency css file content to the
       concated file.
  -H, --Handlebars [mode]  precompile Handlebars template.
       mode = 1, [NOT RECOMMAND] precompile and deal
               Handlebars.compile() in modules
       mode = 2, precompile but keep the Handlebars.compile
       mode = 3, precompile and keep the fn, and insert a Handlebars patch
               on top of the package file(transport or concat)
       mode = 4, do nothing but console.log the patch
       default to 2
  -T, --tplonly            only use tpl(.tpl|.html) even if transported
      tpl(.tpl.js|.html.js) exists too.
  -w, --watch              [tpl only] watch and build templates