0.2.0 • Public • Published

    Devshare Site

    Release Build Status Dependency Status License Code Style


    Customizable open-source collaborative code editor and project building tool

    Visit to begin sharing you development.

    Local Development

    1. Clone repo:
    2. Install dependencies: npm install
    3. Create src/config.js
    4. Run dev server npm run dev

    If everything works, you should see the following:

    While developing, you will probably rely mostly on npm run dev; however, there are additional scripts at your disposal:

    npm run <script> Description
    start Serves your app at localhost:3000. HMR will be enabled in development.
    compile Compiles the application to disk (~/dist by default).
    dev Same as npm start, but enables nodemon for the server as well.
    dev:no-debug Same as npm run dev but disables devtool instrumentation.
    test Runs unit tests with Karma and generates a coverage report.
    test:dev Runs Karma and watches for changes to re-run tests; does not generate coverage reports.
    build Runs linter, tests, and then, on success, compiles your application to disk.
    build:dev Same as build but overrides NODE_ENV to "development".
    build:prod Same as build but overrides NODE_ENV to "production".
    lint Lint all .js files.
    lint:fix Lint and fix all .js files. Read more on this.


    • devshare.js - Main platform functionality (Add/Remove/Update projects, Uploading/Downloading files)

    • redux-devshare - Redux connector for devshare library

    • react - View logic

    • redux - State management

    • webpack - Building/Bundling

    • material-ui - Google Material styling

    Application Structure

    The application structure presented in this boilerplate is fractal, where functionality is grouped primarily by feature rather than file type. Please note, however, that this structure is only meant to serve as a guide, it is by no means prescriptive. That said, it aims to represent generally accepted guidelines and patterns for building scalable applications. If you wish to read more about this pattern, please check out this awesome writeup by Justin Greenberg.

    ├── bin                      # Build/Start scripts
    ├── blueprints               # Blueprint files for redux-cli
    ├── build                    # All build-related configuration
    │   └── webpack              # Environment-specific configuration files for webpack
    ├── config                   # Project configuration settings
    ├── server                   # Koa application (uses webpack middleware)
    │   └── main.js              # Server application entry point
    ├── src                      # Application source code
    │   ├── index.html           # Main HTML page container for app
    │   ├── main.js              # Application bootstrap and rendering
    │   ├── components           # Reusable Presentational Components
    │   ├── containers           # Reusable Container Components
    │   ├── layouts              # Components that dictate major page structure
    │   ├── redux                # "Ducks" location...
    │   │   └── modules          # reducer, action, creators not part of a route
    │   ├── routes               # Main route definitions and async split points
    │   │   ├── index.js         # Bootstrap main application routes with store
    │   │   └── Home             # Fractal route
    │   │       ├── index.js     # Route definitions and async split points
    │   │       ├── assets       # Assets required to render components
    │   │       ├── components   # Presentational React Components
    │   │       ├── container    # Connect components to actions and store
    │   │       ├── modules      # Collections of reducers/constants/actions
    │   │       └── routes **    # Fractal sub-routes (** optional)
    │   ├── static               # Static assets (not imported anywhere in source code)
    │   ├── store                # Redux-specific pieces
    │   │   ├── createStore.js   # Create and instrument redux store
    │   │   └── reducers.js      # Reducer registry and injection
    │   └── styles               # Application-wide styles (generally settings)
    └── tests                    # Unit tests


    Developer Tools

    We recommend using the Redux DevTools Chrome Extension. Using the chrome extension allows your monitors to run on a separate thread and affords better performance and functionality. It comes with several of the most popular monitors, is easy to configure, filters actions, and doesn’t require installing any packages.


    We use react-router route definitions (<route>/index.js) to define units of logic within our application. See the application structure section for more information.


    To add a unit test, simply create a .spec.js file anywhere in ~/tests. Karma will pick up on these files automatically, and Mocha and Chai will be available within your test without the need to import them. If you are using redux-cli, test files should automatically be generated when you create a component or redux module.

    Coverage reports will be compiled to ~/coverage by default. If you wish to change what reporters are used and where reports are compiled, you can do so by modifying coverage_reporters in ~/config/index.js.


    Devshare-site is deployable by serving the ~/dist folder generated by npm run deploy (make sure to specify your target NODE_ENV as well). This project does not concern itself with the details of server-side rendering or API structure, since that demands an opinionated structure that makes it difficult to extend the starter kit. However, if you do need help with more advanced deployment strategies, here are a few tips:

    Static Deployments

    If you are serving the application via a web server such as nginx, make sure to direct incoming routes to the root ~/dist/index.html file and let react-router take care of the rest. If you are unsure of how to do this, you might find this documentation helpful. The Koa server that comes with the starter kit is able to be extended to serve as an API or whatever else you need, but that's entirely up to you.

    Build System


    Default project configuration can be found in ~/config/index.js. Here you'll be able to redefine your src and dist directories, adjust compilation settings, tweak your vendor dependencies, and more. For the most part, you should be able to make changes in here without ever having to touch the actual webpack build configuration.

    If you need environment-specific overrides (useful for dynamically setting API endpoints, for example), you can edit ~/config/environments.js and define overrides on a per-NODE_ENV basis. There are examples for both development and production, so use those as guidelines. Here are some common configuration options:

    Key Description
    dir_src application source code base path
    dir_dist path to build compiled application to
    server_host hostname for the Koa server
    server_port port for the Koa server
    compiler_css_modules whether or not to enable CSS modules
    compiler_devtool what type of source-maps to generate (set to false/null to disable)
    compiler_vendor packages to separate into to the vendor bundle


    Special thanks to @davezuko for creating react-redux-starter-kit which was a huge inspiration




    npm i devshare-site

    DownloadsWeekly Downloads






    Last publish


    • prescottprue