View on GitHub
Download .zip
Download .tar.gz

Parent module responsible currently for installing child modules from applications package.json fearDependencies property. If no parent application is present then installing fear-core will scaffold a recommended (but then configurable) application with some default tasks. Please note scaffold functionality is under development and currently is for demonstration purposes only.

Further reading

The following files will always be copied and overwrite the existing files to the parent application:

config/development/pages/core.js
gulpfile.js

The following will be copied to the parent application only if they don't already exist (i.e a new application is being created):

app/core
config
tasks
mock
app/common
.editorconfig
.eslintrc
.eslintignore
.gitignore

Available modules


Changelog

3.0.17

  • during installation do not overwrite hub page if already exists

3.0.16

  • use mns eslint instead of fear eslint

3.0.6

  • [bug fix] more reliable way of testing for parent application

3.0.5

  • fixed config utility transforming arrays in config files to objects

3.0.4

  • allow fear-core-serve patch version updates

3.0.3

  • point all hub page sass dependencies to core-ui
  • hub page no longer uses angular package

3.0.2

  • update fear-core-serve version

3.0.0

  • replaced $fonthelvetica--light and $fonthelvetica--roman variable references to $font__mns-london for new fear-core-ui fonts
  • update toProcess helper to reflect core-build api changes

2.0.1

  • update to fear-core-build 2.0.0
  • create angular.package.js (with no version in name)

2.0.0

  • update hub page to fear-core-ui 2.0.0

1.4.7

  • fix issue with bundled angular package net returning the right object
  • removed jspm install gulp task

1.4.6

  • update jspm paths to systemJS

1.4.4

  • remove fear-core-app references

1.4.3

  • remove globals in favour of node_module to encapsulate cli args
  • add core app folder that currently has hub page in (replaces fear-core-app)

1.4.0

  • removes custom install in favour of default npm install

1.3.14

  • added disable scaffold flag
  • moved some dependencies to dev dependencies
  • remove copying of jspm configurations at install time

1.3.9

  • improved installation procedure and architecture
  • allow for update of fear-core dependencies

1.3.7

  • application preinstall script added
    • allows for greater control when installing modules when fear-core already installed
    • gulpfile is generated for every npm install including when fear-core already installed

1.3.0

  • implemented dynamic module loading based on cli args
  • implemented dynamic gulpfile based on cli args
  • added mock data tasks
  • improved auto generation of git hub pages from markdown files

1.2.2

  • new mapping for tsop endpoints

1.2.1

  • postinstall hook missing

1.2.0

  • updated to use new fear-core modules (aut/dev/build)

1.1.10

  • add production routes for loyalty/account

1.1.9

  • implemented capability to install new application

1.1.8

  • corrected paths to fear-core-app

1.1.7

  • update jspm configs with new angular package

1.1.6

  • copies jspm test config as same file name as other jspm configs

1.1.5

  • fix bug where fearModules is not defined

1.1.4

  • fix path.join invalid argument bug

1.1.3

  • added documentation
  • created utils for filesystem/install functions


Contributing

Here's the most direct way to get your work merged into the project:

If your work is a new feature or a patch then follow the following workflow

  • Fork the project.
  • Clone down your fork ( git clone git@github.com:[username]/fear-core.git ).
  • Create a topic branch to contain your change ( git checkout -b my_awesome_feature ).
  • Code away and add tests if applicable. Not necessarily in that order.
  • Make sure everything still passes by running npm run test.
  • Update the change log with details of the change under the corresponding heading (new feature/patch) - create the heading if it doesnt already exist. The version of the next published version will then be decided by this.
  • If necessary, rebase your commits into logical chunks, without errors.
  • Push the branch up ( git push origin my_awesome_feature ).
  • Create a pull request against fear-core-ui/master and describe what your change does and the why you think it should be merged.

If your work is a breaking change please come to talk to the core team before commencing development.