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.
yarn install
to install dependenciesbin/cli
to use the cli of quasarbin/watch
to automate jobs using json files in the /json folderbin/web
to run an api and web server with form @ http://localhost:3000
bin/cli
to run the application as a process
--runAsDaemon=true
argument to run the web api or watch jobs tasks in the background--runWebApi=true
argument to run the api @ http://localhost:2720
--watchJobs=true
argument to autoload json files to build quasars--runWebform=true
to run the webform @ http://localhost:3000
--autoBuildWebForm=true
to build the quasarWebform task on startup--autoBuildWebApp=true
to build the quasarWebApp task on startup--reRun=true
to rebuild the last successfully run arguments back through quasarbin/package
to create an executable that you can distribute as a standalone applicationFiles 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.