A template for starting front-end projects. Webpack for
require system, build
pipeline, and development server. Boostrap and Handlebars.js included. No
front-end frameworks included.
At the beginning of each cohort, update the versions in
package.json by replace all versions with a glob (
npm update --save && npm update --save-dev. You may wish to test these
changes by deleting the
node_modules directory and running
Fix any conflicts.
- Download this template.
- Unzip and rename the template directory.
README.mdand fill with your own content.
- Move into the new project and
- Install dependencies with
Dependencies are stored in
Do not configure
grunt packages directly in the
Gruntfile.js. Instead, store configurations in the
grunt directory. You won't need a top-level key, since that's
generated by the
Gruntfile.js based on the filename of the configuration
object stored in the
The "manifest" or entry-point is
assets/scripts/index.js. In general, only
application initialization goes in this file. It's normal for developers to
start putting all code in this file, but encourage them to break out different
responsibilities and use the
require syntax put references where they're
Developers should set
config.apiOrigins.development if it differs from the default). With
apiOrigins set, developers may rely on
config.apiOrigin as the base for API
Developers should use getFormFields to retrieve form data to send to an API.
To deploy a browser-template based SPA, run
Developers should run these often!
grunt nagor just
grunt: runs code quality analysis tools on your code and complains
grunt reformat: reformats all your code in a standard style
grunt <server|serve|s>: generates bundles, watches, and livereloads
grunt test: runs any automated tests, depends on
grunt build: place bundled styles and scripts where
index.htmlcan find them
- All content is licensed under a CCBYNCSA 4.0 license.
- All software code is licensed under GNU GPLv3. For commercial use or alternative licensing, please contact email@example.com.