mirror of
https://github.com/embarklabs/embark.git
synced 2025-01-23 20:19:33 +00:00
5ea4807c90
Add an `enabled` property to the pipeline config. This lets developers disable the pipeline using the config file. Updates to the enabled property will be reflected while embark is running. For example if embark is running with the pipeline, setting `enabled: false` in the pipeline config will build/deploy the contracts but not run the pipeline. Conversely, if embark is running with the pipeline disabled, enabling the pipeline in the config will build/deploy the contracts then build the dapp.
28 lines
1.3 KiB
JavaScript
28 lines
1.3 KiB
JavaScript
// Embark has support for Flow enabled by default in its built-in webpack
|
|
// config: type annotations will automatically be stripped out of DApp sources
|
|
// without any additional configuration. Note that type checking is not
|
|
// performed during builds.
|
|
|
|
// To enable Flow type checking refer to the preconfigured template:
|
|
// https://github.com/embark-framework/embark-flow-template
|
|
// A new DApp can be created from that template with:
|
|
// embark new --template flow
|
|
|
|
module.exports = {
|
|
typescript: false,
|
|
// Setting `typescript: true` in this config will disable Flow support in
|
|
// Embark's default webpack config and enable TypeScript support: .ts and
|
|
// .tsx sources will automatically be transpiled into JavaScript without any
|
|
// additional configuration. Note that type checking is not performed during
|
|
// builds.
|
|
|
|
// To enable TypeScript type checking refer to the preconfigured template:
|
|
// https://github.com/embark-framework/embark-typescript-template
|
|
// A new DApp can be created from that template with:
|
|
// embark new --template typescript
|
|
enabled: true
|
|
// Setting `enabled: false` in this config will disable Embark's built-in Webpack
|
|
// pipeline. The developer will need to use a different frontend build tool, such as
|
|
// `create-react-app` or Angular CLI to build their dapp
|
|
};
|