A standalone toolkit for rapid Enact app development.
All that's needed to install @enact/cli is to use npm to install it globally. For Linux
sudo may be required.
npm install -g @enact/cli
Note: Node 6.x or greater required.
Creating a new App
The only time you're ever want to directly use the Enact CLI is when you want to create a new project.
enact create [directory]
This will generate a basic App template, complete with npm scripts and dependencies. If no directory path is specified, it will be generated within the working directory.
Advanced: If you've used
npm linkon separate installations of the Enact repo, you can run
enact linkafterwards to link in any available Enact libraries.
Enact supports several commands, each accessible through the
enact command and through npm aliases in package.json. For help on individual commands, add
--help following the command name. The commands are:
enact serve (aliased as
npm run serve)
Builds and serves the app in the development mode.
Open http://localhost:8080 to view it in the browser.
The page will reload if you make edits.
enact pack (aliased as
npm run pack,
npm run pack-p, and
npm run watch)
Builds the project in the working directory. Specifically,
pack builds in development mode with code un-minified and with debug code included, whereas
pack-p builds in production mode, with everything minified and optimized for performance. Be sure to avoid shipping or performance testing on development mode builds.
enact clean (aliased as
npm run clean)
Deletes previous build fragments from ./dist.
enact lint (aliased as
npm run lint)
Runs the Enact configuration of ESLint on the project for syntax analysis.
enact test (aliased as
npm run test and
npm run test-watch)
These tasks will execute all valid tests (files that end in
-specs.js) that are within the project directory. The
test is a standard single execution pass, while
test-watch will set up a watcher to re-execute tests when files change.
enact license (aliased as
npm run license)
Outputs a JSON representation of the licenses for modules referenced by the current project as well as any licenses of modules used by
@enact/cli that may be included in a production build of an app.
Enact Build Options
The @enact/cli tool will check the project's package.json looking for an optional
enact object for a few customization options:
template[string] - Filepath to an alternate HTML template to use with the Webpack html-webpack-plugin.
isomorphic[string] - Alternate filepath to a custom isomorphic-compatible entry point. Not needed if main entry point is already isomorphic-compatible.
title[string] - Title text that should be put within the HTML's
<title></title>tags. Note: if this is a webOS-project, the title will, by default, be auto-detected from the appinfo.json content.
theme[object] - A simplified string name to extrapolate
screenTypespreset values from. For example,
fontGenerator[string] - Filepath to a CommonJS fontGenerator module which will build locale-specific font CSS to inject into the HTML. By default, will use any preset for a specified theme or fallback to moonstone.
ri[object] - Resolution independence options to be forwarded to the LESS plugin. By default, will use any preset for a specified theme or fallback to moonstone
screenTypes[array|string] - Array of 1 or more screentype definitions to be used with prerender HTML initialization. Can alternatively reference a json filepath to read for screentype definitons. By default, will use any preset for a specified theme or fallback to moonstone.
nodeBuiltins[object] - Configuration settings for polyfilling NodeJS built-ins. See
externalStartup[boolean] - Flag whether to externalize the startup/update js that is normally inlined within prerendered app HTML output.
target[string|array] - A build-type generic preset string (see
targetwebpack option) or alternatively a specific browserlist array of desired targets.
proxy[string] - Proxy target during project
serveto be used within the http-proxy-middleware.
..."enact":"theme": "moonstone""nodeBuiltins":fs: 'empty'net: 'empty'tls: 'empty'...
Displaying Lint Output in the Editor
Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.
They are not required for linting. You should see the linter output right in your terminal. However, if you prefer the lint results to appear right in your editor, there are some extra steps you can do.
You would need to install an ESLint plugin for your editor first.
A note for Atom
If you are using the Atom
linter-eslintplugin, make sure that Use global ESLint installation option is checked:
Then, you will need to install some packages globally:
npm install -g eslint eslint-plugin-react eslint-plugin-babel babel-eslint eslint-plugin-enact eslint-config-enact
Copyright and License Information
Unless otherwise specified, all content, including all source code files and documentation files in this repository are:
Copyright (c) 2016-2018 LG Electronics
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Portions of this project are based upon create-react-app, Copyright (C) 2016-present Facebook, Inc.