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

lila-webpack-lib

v0.6.0

Published

wrapped webpack plugin for building a library

Downloads

1

Readme

lila-webpack-lib

Wrapped webpack plugin for building a library.

install

npm install --save-dev lila-webpack-lib

use

In lila.js:

import webpackPlugin from 'lila-webpack-lib';

export default lila => {
  webpackPlugin(lila);

  ...
};

extended commands

start: start a local server to develop an entry

lila start entry

build: pack source codes to distribution bundles

lila build entry1 entry2 entry3 ...

If entry is not provided, @lila/index will be used as default.

extended tasks

@lila/webpack: run webpack

'@lila/webpack'

settings need to be implemented

webpackConfigGenerator: generate webpack config

webpack => ({entry, args, argv, cmd, config, lila}) => config

settings can be implemented

getEntries: get all entries with imported entries, when you want to use *, all special mark

(entries, root, srcDir) => allEntries;

extended configs

forceGet: force all ajax methods as get

type: bool default: true

Normally, only get method can access static file, and post, put, delete ... will cause 404.

mock: use js files to generate mock data

type: bool default: true

In most occasions, you can use json files to provide mock data, but when we want dynamic data, json files won't work.

url: /api/user/profile?id=1

First try /api/user/profile.js:

// export a function, an object, a string
export default (req, res) => {
  // do everything you want
};

// or export an object, a string(not function)
export default {
  success: true,
  message: 'ok',
  data: { ... },
};

Second try /api/user.js:

// export a function
export const profile = (req, res) => {
  // do everything you want
};

// or export an object, a string(not function)
export const profile = {
  success: true,
  message: 'ok',
  data: { ... },
}

req, res refers to Node Http, and file name should not contain . character, or it will be treated as a static file.

mockRoot: extra mock root url prefix(relative to root)

type: string/function

When use mock data, maybe you don't like url to be that long, such as use /one/page/mock/list to access /one/page/mock/list.js file.

Lila internally provide a convenient way to do that.

If url try to get a mock data from /one/page/mock/list.js file, lila will try urls in sequences as follows:

  1. ${url}: try itself /one/page/mock/list
  2. /mock/${url}: try mock prefix
  3. /${entry}/${url}: try under entry's workspace, you can use /mock/list
  4. /${entry}/mock/${url}: try mock prefix under entry's workspace, you can use /list

If you want more convenient ways, you can add your own ways by mockRoot.

// a string
mockRoot: '/some/directory'

// strings
mockRoot: ['/first/directory', '/second/directory']

// return a string
mockRoot: (entry, lila) => '/some/directory';

// return strings
mockRoot: (entry, lila) => ['/first/directory', '/second/directory']

port: local server port

type: number default: 8090

browserSync: browser-sync config

type: {} default: {}

devMiddleware: webpack-dev-middleware config

type: {} default: { watchOptions: { ignored: /node_modules/ } }

hotMiddleware: webpack-hot-middleware config

type: {} default: {}

npm packages