Get Started

1. Clone the project

   git clone https://github.com/Liceth/owl.git.

2. Run the setup script

   npm start -s

3. Review the app.

   This repository include a working widget, which renders N last social posts from the given JSON feed. The widget should pull updates from the feed with the given interval and update the displayed list by removing old items and displaying the new ones, so the most recent N posts will be displayed. Note how all source code is placed under /src. Tests are placed alongside the file under test. The final built app is placed under /dist. These are the files you run in production.

Initial Machine Setup

1. Install Node 4.0.0 or greater

   (5.0 or greater is recommended for optimal build performance) Need to run multiple versions of Node? Use nvm.

2. Install Git.

3. Disable safe write in your editor to assure hot reloading works properly.

4. Complete the steps below for your operating system:

   macOS

   • Install watchman via brew install watchman or fswatch via brew install fswatch to avoid this issue which occurs if your macOS has no appropriate file watching service installed.

   Linux

   • Run this to increase the limit on the number of files Linux will watch. Here's why.

     echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p.

   Windows

   • Install Python 2.7. Some node modules may rely on node-gyp, which requires Python on Windows.

   • Install C++ Compiler. Browser-sync requires a C++ compiler on Windows.

     Visual Studio Express comes bundled with a free C++ compiler.

     If you already have Visual Studio installed: Open Visual Studio and go to File -> New -> Project -> Visual C++ -> Install Visual C++ Tools for Windows Desktop. The C++ compiler is used to compile browser-sync (and perhaps other Node modules).

---

Having Issues? Try these things first

1. Make sure you ran all steps in Get started including the initial machine setup.

2. Run npm install - If you forget to do this, you'll see this: babel-node: command not found.

3. Install the latest version of Node. Or install Node 5.12.0 if you're having issues on Windows. Node 6 has issues on some Windows machines.

4. Make sure files with names that begin with a dot (.editorconfig, .gitignore, .npmrc) are copied to the project directory root. This is easy to overlook if you copy this repository manually.

5. Don't run the project from a symbolic link. It may cause issues with file watches.

6. Delete any .eslintrc that you're storing in your user directory. Also, disable any ESLint plugin / custom rules that you've enabled within your editor. These will conflict with the ESLint rules defined in this project.

7. Make sure you don't have NODE_ENV set to production on your machine. If you do then the development dependencies won't be installed. Here's how to check.

8. Install watchman with brew install watchman if you are having the following error after an initial npm start -s:

   2017-09-05 00:44 node[68587] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
   2017-09-05 00:44 node[68587] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
   events.js:160
         throw er; // Unhandled 'error' event
         ^
   
   Error: Error watching file for changes: EMFILE
       at exports._errnoException (util.js:1022:11)
       at FSEvent.FSWatcher._handle.onchange (fs.js:1406:11)

9. Tip: Things to check if you get an npm run lint error or build error:

   • If ESW found an error or warning in your project (e.g. console statement or a missing semi-colon), the lint thread will exit with Exit status 1. To fix:

     1. Change the npm run lint script to "esw webpack.config.* src tools; exit 0"
     2. Change the npm run lint:watch script to "esw webpack.config.* src tools --watch; exit 0"

     Note: Adding exit 0 will allow the npm scripts to ignore the status 1 and allow ESW to print all warnings and errors.

   • Ensure the eslint/esw globally installed version matches the version used in the project. This will ensure the esw keyword is resolved.

10. Rebuild node-sass with npm rebuild node-sass if you are having and error like Node Sass does not yet support your current environment on macOS XXX after an initial npm start -s.

---

Technologies

Slingshot offers a rich development experience using the following technologies:

Tech	Description	Learn More
React	Fast, composable client-side components.	Pluralsight Course
Redux	Enforces unidirectional data flows and immutable, hot reloadable store. Supports time-travel debugging. Lean alternative to Facebook's Flux.	Getting Started with Redux, Building React Applications with Idiomatic Redux, Pluralsight Course
React Router	A complete routing library for React	Pluralsight Course
Babel	Compiles ES6 to ES5. Enjoy the new version of JavaScript today.	ES6 REPL, ES6 vs ES5, ES6 Katas, Pluralsight course
Webpack	Bundles npm packages and our JS into a single file. Includes hot reloading via react-transform-hmr.	Quick Webpack How-to Pluralsight Course
Browsersync	Lightweight development HTTP server that supports synchronized testing and debugging on multiple devices.	Intro vid
Jest	Automated tests with built-in expect assertions and Enzyme for DOM testing without a browser using Node.	Pluralsight Course
TrackJS	JavaScript error tracking.	Free trial
ESLint	Lint JS. Reports syntax and style issues. Using eslint-plugin-react for additional React specific linting rules.
SASS	Compiled CSS styles with variables, functions, and more.	Pluralsight Course
PostCSS	Transform styles with JS plugins. Used to autoprefix CSS
Editor Config	Enforce consistent editor settings (spaces vs tabs, etc).	IDE Plugins
npm Scripts	Glues all this together in a handy automated build.	Pluralsight course, Why not Gulp?

---

Questions?

Check out the FAQ

owl