| Package | quasar |
| Description | |
| Node Version | >= 6.0.0 |
| Gulp Version | >= 4.0.0 |
Quasar is a build pipeline and application runtime that you can use to build web snippets of html with embedded javascript and css.
You can read more about this project:
run bin/app to install and run the entire application in an electron app complete with api and webserver. You do not need to follow any additional steps if all you want to do is use quasar as an application.
- install nodejs
- run
yarn installto install dependencies
- run
bin/clito use the cli of quasar - run
bin/watchto automate jobs using json files in the /json folder - run
bin/webto run an api and web server with form @ http://localhost:3000
- run
bin/clito run the application as a process- optionall add the
--runAsDaemon=trueargument to run the web api or watch jobs tasks in the background - optionally add the
--runWebApi=trueargument to run the api @ http://localhost:2720 - optionally add the
--watchJobs=trueargument to autoload json files to build quasars - optionally add the
--runWebform=trueto run the webform @ http://localhost:3000 - optionally add the
--autoBuildWebForm=trueto build the quasarWebform task on startup - optionally add the
--autoBuildWebApp=trueto build the quasarWebApp task on startup - optionally add the
--reRun=trueto rebuild the last successfully run arguments back through quasar
- optionall add the
- run
bin/packageto create an executable that you can distribute as a standalone application
Files located in the /assets folder are used in build tasks for quasar ouput. The default target of a quasar is ${qType}.hml, so if the quasar is of type 'page' then the default target would be page.html. Similarly, css and js assets are defaulted to ${qType}.css and ${qType}.js respectively. These default values can be overriden at runtime.
Logging to the console from the CLI happens with data off by default and only the most top level messages. Other debug options are set with the argument --log= and available options are ALL,DEBUG,NONE,NODATA. Successful build outputs are logged in a '.log' file in the root of the project.