• Introduction
• Project Structure
• assets
  • css
    • loading-screen.css
    • main.css
  • images
    • favicon.png
    • logo.png
  • less
    • loading-screen.less
    • main.less
  • sass
    • loading-screen.scss
    • main.scss
• config
  • env
    • development.js
    • production.js
  • actions
  • auth
  • collections
  • connect
  • connections
  • local
  • models
  • react
  • reducers
  • redux
  • router
• initializers
  • .gitkeep
• src
  • actions
    • .gitkeep
  • collections
    • .gitkeep
  • components
    • Layout.js
    • Master.js
  • constants
    • ActionTypes.js
    • PayloadStates.js
  • decorators
    • UserIsAuthenticated.js
    • UserIsAuthorized.js
  • dialogs
    • .gitkeep
  • forms
    • .gitkeep
  • models
    • .gitkeep
  • reducers
    • .gitkeep
  • utils
    • auth.js
    • storageAvailable.js
• .babelrc
• .editorconfig
• .gitignore
• .lorerc
• db.json
• index.html
• index.js
• package.json
• package-lock.json
• postcss.config.js
• README.md
• routes.js
• webpack.config.js

.babelrc

This file contains the settings for the preset and plugins that determine how your project is transpiled.

To learn more about this file, see the .babelrc documentation on the Babel website.

Note about babel-preset-env

When you run npm install you may see the deprecation warning below in the console:

babel-preset-es2015@6.24.1: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

Lore is intentionally (at least for now) avoiding the use of babel-preset-env for the following reasons:

• There is an issue where you cannot control the preset ordering, which prevents it from working with some plugins like transform-class-properties and transform-decorators-legacy.
• Those plugins are used for the esnext version of a Lore project, which means the project types would end up with inconsistent babel configurations.

Starting in Babel 7, transform-decorators will be included in Babel's Stage-0 presets, and the configuration will be moving to a .babel.js file to allow you to programmatically construct your configuration.

Those changes may make it feasible to adopt babel-preset-env, but in the meantime, if the issues described above don't concern you, feel free to change your Babel setup to use babel-preset-env.

Defaults

The default file included in new projects looks like this:

{
  "presets": [
    "es2015",
    "react"
  ],
  "plugins": []
}

{
  "presets": [
    "es2015",
    "react"
  ],
  "plugins": []
}

{
  "presets": [
    "es2015",
    "react",
    "stage-2"
  ],
  "plugins": [
    "transform-decorators-legacy"
  ]
}