prime-cli v1.0.0
Polymer Redefined In Mobile Environment
Prime-CLI
A command-line tool for Prime projects.
This project is intended to make it easier building cordova project with polymer.
This project is still in alpha so don't expect too much, but most of basic commands is working because it's based on polymer-cli.
Overview
Prime-CLI includes a number of tools for working with Polymer,Web Components and Cordova:
- init - Initializes a Prime project from one of several templates
- build - Builds an application-style project
- lint - Lints the project
- serve - Runs a development server
- test - Runs tests with web-component-tester
- platforms - Add or remove specific platform
- plugin - Add or remove cordova plugin
Installation
Install via npm:
$ npm install -g prime-cliThen run via prime <command>:
$ prime helpProject Structure
Polymer-CLI is somewhat opinionated about project structure.
There are two type of projects:
Plugin projects TODO: write this when plugin environment is implemented.
Application projects
Application projects are self-contained and intended to be deployed as a standalone application. Application projects contain elements in a
src/folder and import their dependencies with absolute paths, or relative paths that reference folders inside the project folder.
Application Styles
Prime-CLI currently supports two styles of applications:
Monolithic applications, which have a single entrypoint (usually index.html) and eagerly import all dependencies.
"App shell" applications, which have a very lightweight entrypoint, an app-shell with startup and routing logic, and possibly lazy loaded fragments.
App-shell Structure
App-shell apps are currently the preferred style for Polymer CLI, and most commands are being optimized to support them. App-shell apps usually have client-side routing (see the app-route element), and lazy load parts of the UI on demand.
Prime-CLI supports this style by understand these different types of files:
- entrypoint - The first file served by the web server for every valid route (usually index.html). This file should be very small, since it may not cache well and must reference resources with absolute URLs, due to being served from many URLs.
- shell - The actual app shell, which includes the top-level logic, routing, and so on.
- fragments - lazy loaded parts of the application, typically views and other elements loaded on-demand.
Configuration
The project files are specified either as global flags: --entrypoint, --shell and zero or more --fragment flags, or in a prime.json configuration file.
prime.json
You can specify the project files in prime.json so that commands like prime build work without flags:
{
"rootDir": "src",
"outDir": "www",
"entrypoint": "index.html",
"shell": "src/my-app/my-app.html",
"fragments": [
"src/app-home/app-home.html",
"src/app-view-1/app-view-1.html",
],
"sources": [
"src/**/*",
"images/**/*",
"bower.json"
],
"includeDependencies": [
"bower_components/additional-files-to-include-in-build/**/*",
"bower_components/webcomponentsjs/webcomponents-lite.js"
],
"plugins": {
"cordova-plugin-facebook4":{
"version":"",
"variable":{
"APP_ID":"123456789",
"APP_NAME":"myApplication"
}
},
"cordova-plugin-console":{
"version":"1.0.0"
}
},
"platforms": {
"android":{
"version":"6.0"
}
}
}Commands
help
Displays help on commands and options:
$ prime helpinit
Initializes a Prime project from one of several templates.
Choose a template from a menu:
$ prime initCreate a new project from the 'element' template:
$ prime init applicationinstall
Installs Bower dependencies, optionally installing multiple variants.
$ prime installThis performs a Bower install of dependencies listed in bower.json, and is
equivalent to bower install.
$ prime install --variantsThis performs a Bower install, and also installs any dependency variants
specified in the "variants" property of bower.json.
lint
With a prime.json file:
$ prime lintSpecifying a file to lint:
$ prime lint index.htmltest
Run test with web-component-tester:
$ prime testbuild
Specify project files as flags:
$ prime build --entrypoint index.html --shell src/my-app/my-app.htmlUse index.html as the entrypoint, or read from prime.json:
$ prime buildbuild is opinionated and defaults to a good build for app-shell apps. It writes the built output to build/bundled and build/unbundled folders. Both outputs have been run though HTML, JS and CSS optimizers, and have a Service Worker generated for them. The bundled folder contains the application files process by Vulcanize, Polymer's HTML bundler, for optimal loading via HTTP/1. The unbundled folder is optimized for HTTP/2 + Push.
While the build command should support most projects, some users will need greater control over their build pipeline. If that's you, check out the prime-build library. Prime-build can be called and customized programmatically, giving you much greater control than the CLI can provide.
serve
Start the development server:
$ prime serveStart the development server, and open the default browser:
$ prime serve -oBy default the server listens to localhost. To listen to a different address use the --hostname flag. For example:
$ prime serve -o --hostname 0.0.0.0platforms
Add platform into project:
$ prime platforms add androidRemove platforms from project:
$ prime platforms remove androidplugin
Install cordova plugin:
$ prime plugin add cordova-plugin-nameInstall cordova plugin with variable:
$ prime plugin add cordova-plugin-name --variable VARIABLE_NAME=valueInstall multiple plugins:
$ prime plugin add cordova-plugin-name-1 cordova-plugin-name-2Templates and Generators
Prime-CLI initializes new projects with the init command, and includes
a few built-in templates.
New templates can be distributed and installed via npm. Yeoman generators
prefixed with generator-prime-init will show up in the prime init
menu.
Compiling from Source
$ npm run buildYou can compile and run the CLI from source by cloning the repo from Github and then running npm run build. But make sure you have already run npm install before building.
Supported node.js versions
Prime CLI targets the current LTS version (4.x) of Node.js and later.