@spryker/oryx-for-zed

oryx for Zed (beta)

Spryker ZED frontend automation tool (oryx based)

1. Introduction
2. Requirements
3. Setup
4. Usage
5. API

For more info about oryx, click here.

Introduction

This is an extension of oryx that performs a full build for Spryker Zed UI applications. It also provides access to Zed settings and Zed webpack configuration, so you are able to extend/change the whole building process.

Requirements

• nodejs version 6.x LTS
• npm version >= 3.x or yarn version >= 0.19.x

Setup

You need to add oryx-for-zed to your package.json; open the terminal, go to your project root folder and type:

npm install @spryker/oryx-for-zed --save-dev
# or 
yarn add @spryker/oryx-for-zed --dev

oryx-for-zed comes with a peer dependency:

• oryx version >= 0.3.x

Usage

Once installed, you can:

• call the builder directly from your scripts (simple builder)
• extend/change the settings/webpack configuration for your custom Zed build

Simple builder

The easiest way to run oryx-for-zed is to add a script to your package.json:

{
    "scripts": {
        "build-zed": "node ./node_modules/@spryker/oryx-for-zed/build"
    }
}

Then just open the terminal and type:

npm run build-zed
# or 
yarn run build-zed

Extend/change settings

If you want to customise settings, just rely on onyx-for-zed API. The following example shows how to create a custom build.

build.js

Create a build.js file in your project containing your custom settings and the logic needed to get the webpack configuration and run the builder:

const oryx = require('@spryker/oryx');
const oryxForZed = require('@spryker/oryx-for-zed');

const myCustomZedSettings = Object.assign({}, oryxForZed.settings, {
    // your own settings
});

const configuration = oryxForZed.getConfiguration(myCustomZedSettings);

oryx.build(configuration);

package.json

Add a script into your package.json pointing to build.js.

{
    "scripts": {
        "build-zed": "node ./path/to/build"
    }
}

Extend/change webpack configuration

If you want to customise the webpack configuration, just rely on onyx-for-zed API. The following example shows how to create a custom build.

webpack.config.js

Create a webpack.config.js file in your project containing your webpack custom configuration:

const oryxForZed = require('@spryker/oryx-for-zed');
const oryxConfiguration = oryxForZed.getConfiguration(oryxForZed.settings);

const myCustomZedConfiguration = Object.assign({}, oryxConfiguration, {
    // your own configuration
});

module.exports = myCustomZedConfiguration;

build.js

Create a build.js file in your project containing your webpack configuration and the logic needed to run the builder:

const oryx = require('@spryker/oryx');
const myCustomZedConfiguration = require('./webpack.config.js');

oryx.build(myCustomZedConfiguration);

package.json

Add a script into your package.json pointing to build.js.

{
    "scripts": {
        "build-zed": "node ./path/to/build"
    }
}

API

• settings
• getConfiguration()
• CLI args

settings

oryxForZed.settings

Contain all the basic setting used in the webpack configuration.

Look here (code) for more details.

getConfiguration()

oryxForZed.getConfiguration(settings)

Return the default Zed webpack configuration, based on provided settings.

Look here (code) for more details.

CLI args

oryx-for-zed uses some arg to customise the build process. You can pass them using the terminal:

npm run script-name -- --arg
# or 
yarn run script-name -- --arg

Or embedding them into the script section in package.json:

{
    "scripts": {
        "build-zed": "node ./node_modules/@spryker/oryx-for-zed/build --arg"
    }
}

Args list

• --dev: development mode; enable webpack watchers on the code
• --prod: production mode; enable assets optimisation/compression
• --boost: build boost mode (experimental); build assets using eval source maps

If no arg is passed, development is activated but without watchers.

Changelog

0.5.5 (beta)

Released on 29.03.2017

• update webpack configuration to remove errors introduced due to webpack update
• update dependecies:
  • webpack ~2.2.0 > ~2.3.2