yProx-CLI

Assets and entries

Implying you have this configuration:

// yprox-cli.config.js

module.exports = {
  assets: {
    app: './assets/app.js',
  },

  path: {
    js: './public/js',
    css: './public/css',
  },
};

Assets

You should create ./assets/app.js file that will export a function:

// `api` is an instance of `API` class
// `config` is your configuration (`yprox-cli.config.js`)
module.exports = (api, config) => {
  return [ // array of entries
    { ... },
    { ... }
  ];
}

If you have few entries to define, you can directly use a function or even an array:

// yprox-cli.config.js

module.exports = {
  assets: {
    // the file will be included
    app: './assets/app.js',

    // with a function
    app: (cli, config) => ([
      { ... },
      { ... },
    ]),

    // with an array, useful if you put your config inside your `package.json`
    app: [
      { ... },
      { ... }
    ]
  },
  // ...
}

Entries

An entry defines:

  • what will be build (source files)
  • how to build it (handler)
  • where output it (destination path)

This is what an entry looks like:

{
  handler: 'sass',
  src: 'src/CoreBundle/Resources/private/sass/grid.scss',
  concat: 'my-grid.css',
  dest: config.path.css,

  // optional
  sourceMaps: false // force enable/disable source maps generation, default to `api.isProduction()`
},

← Handlers→