Lila-webpack-lib NPM

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:

${url}: try itself /one/page/mock/list
/mock/${url}: try mock prefix
/${entry}/${url}: try under entry's workspace, you can use /mock/list
/${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']