neves / movies

🍿 react-app for movies

Movies ^{_{react-app for movie related search}}

This repo contains all the code for the movies.vitordino.com app.

_{this project is built upon significa/frontend-challenge, all design credits go for them.}

_{This product uses the TMDb API but is not endorsed or certified by TMDb.}

Development Quick Start

Make sure your system meets the required dependencies and versions before proceeding.

Get one themoviedb.org API key, and set it as a environment variable named REACT_APP_TMDB_KEY (you can use a .env.local file for that)

# Install project dependencies
$ yarn

# Development server
$ yarn dev # starts dev server

# Build app
$ yarn build # Outputs to ./build directory
$ npx serve build # Static server for the built website

Development Server Options

To change the port set the PORT environment variable:

$ PORT=9000 yarn dev
# => starts server at http://localhost:9000

Tech Stack

Key Front-End Packages

name	license	description
react	MIT	Declarative, component-based, functional aproach to user interfaces
create-react-app v2	MIT	create react apps with no build configuration.
styled-components	MIT	css-in-js library, composable styling
@reach/router	MIT	Next Generation Routing for react
rescripts	MIT	Use the latest react-scripts with custom configurations for Babel, ESLint, TSLint, Webpack,... ∞
react-snap	MIT	Zero-configuration framework-agnostic static prerendering for SPAs

_{This app is heavily built on react new features — eg.: hooks, lazy and Suspense.}

System Dependencies

name	min. version
git	2.0.0
bash	3.0.0
node	8.0.0
yarn	1.0.0

movies's Issues

teste

funciona?

An in-range update of styled-components is breaking the build 🚨

The dependency styled-components was updated from 4.2.0 to 4.2.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

styled-components is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

• • The devDependency @babel/plugin-proposal-export-default-from was updated from 7.8.0 to 7.8.3.

• The devDependency @babel/plugin-proposal-optional-chaining was updated from 7.8.0 to 7.8.3.
• The devDependency @babel/plugin-syntax-dynamic-import was updated from 7.8.0 to 7.8.3.
• The devDependency @babel/plugin-transform-runtime was updated from 7.8.0 to 7.8.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.