Start checkin-portal

npm-debug.log

+0 info it worked if it ends with ok
+1 verbose cli [ '/home/gustavo/.nvm/versions/node/v6.9.0/bin/node',
+1 verbose cli   '/home/gustavo/.nvm/versions/node/v6.9.0/bin/npm',
+1 verbose cli   'start' ]
+2 info using npm@3.10.8
+3 info using node@v6.9.0
+4 verbose stack Error: ENOENT: no such file or directory, open '/home/gustavo/Documentos/SMPPIR-Checkin-Portal/package.json'
+4 verbose stack     at Error (native)
+5 verbose cwd /home/gustavo/Documentos/SMPPIR-Checkin-Portal
+6 error Linux 4.13.0-41-generic
+7 error argv "/home/gustavo/.nvm/versions/node/v6.9.0/bin/node" "/home/gustavo/.nvm/versions/node/v6.9.0/bin/npm" "start"
+8 error node v6.9.0
+9 error npm  v3.10.8
+10 error path /home/gustavo/Documentos/SMPPIR-Checkin-Portal/package.json
+11 error code ENOENT
+12 error errno -2
+13 error syscall open
+14 error enoent ENOENT: no such file or directory, open '/home/gustavo/Documentos/SMPPIR-Checkin-Portal/package.json'
+15 error enoent ENOENT: no such file or directory, open '/home/gustavo/Documentos/SMPPIR-Checkin-Portal/package.json'
+15 error enoent This is most likely not a problem with npm itself
+15 error enoent and is related to npm not being able to find a file.
+16 verbose exit [ -2, true ]

smppir-checkin-portal/.gitignore

+# See https://help.github.com/ignore-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+
+# testing
+/coverage
+
+# production
+/build
+
+# misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

smppir-checkin-portal/Log.md

+*Projeto SMPPIR-Checkin-Portal criado no git
+**cd SMPPIR-Checkin-Portal/

smppir-checkin-portal/package.json

+{
+  "name": "smppir-checkin-portal",
+  "version": "0.1.0",
+  "private": true,
+  "dependencies": {
+    "react": "^16.3.2",
+    "react-dom": "^16.3.2",
+    "react-scripts": "1.1.4"
+  },
+  "scripts": {
+    "start": "react-scripts start",
+    "build": "react-scripts build",
+    "test": "react-scripts test --env=jsdom",
+    "eject": "react-scripts eject"
+  }
+}
\ No newline at end of file

smppir-checkin-portal/public/MaterialIcons.css

+@font-face {
+  font-family: 'Material Icons';
+  font-style: normal;
+  font-weight: 400;
+  src: url(./icons/iconfont/MaterialIcons-Regular.eot); /* For IE6-8 */
+  src: local('Material Icons'),
+        local('MaterialIcons-Regular'),
+        url(./icons/iconfont/MaterialIcons-Regular.woff2) format('woff2'),
+        url(./icons/iconfont/MaterialIcons-Regular.woff) format('woff'),
+        url(./icons/iconfont/MaterialIcons-Regular.ttf) format('truetype');
+}
+
+.material-icons {
+  font-family: 'Material Icons';
+  font-weight: normal;
+  font-style: normal;
+  font-size: 24px;
+  line-height: 1;
+  letter-spacing: normal;
+  text-transform: none;
+  display: inline-block;
+  white-space: nowrap;
+  word-wrap: normal;
+  direction: ltr;
+}

smppir-checkin-portal/public/icons/iconfont/README.md

+The recommended way to use the Material Icons font is by linking to the web font hosted on Google Fonts:
+
+```html
+<link href="https://fonts.googleapis.com/icon?family=Material+Icons"
+      rel="stylesheet">
+```
+
+Read more in our full usage guide:
+http://google.github.io/material-design-icons/#icon-font-for-the-web

smppir-checkin-portal/public/icons/iconfont/material-icons.css

+@font-face {
+  font-family: 'Material Icons';
+  font-style: normal;
+  font-weight: 400;
+  src: url(MaterialIcons-Regular.eot); /* For IE6-8 */
+  src: local('Material Icons'),
+       local('MaterialIcons-Regular'),
+       url(MaterialIcons-Regular.woff2) format('woff2'),
+       url(MaterialIcons-Regular.woff) format('woff'),
+       url(MaterialIcons-Regular.ttf) format('truetype');
+}
+
+.material-icons {
+  font-family: 'Material Icons';
+  font-weight: normal;
+  font-style: normal;
+  font-size: 24px;  /* Preferred icon size */
+  display: inline-block;
+  width: 1em;
+  height: 1em;
+  line-height: 1;
+  text-transform: none;
+  letter-spacing: normal;
+  word-wrap: normal;
+  white-space: nowrap;
+  direction: ltr;
+
+  /* Support for all WebKit browsers. */
+  -webkit-font-smoothing: antialiased;
+  /* Support for Safari and Chrome. */
+  text-rendering: optimizeLegibility;
+
+  /* Support for Firefox. */
+  -moz-osx-font-smoothing: grayscale;
+
+  /* Support for IE. */
+  font-feature-settings: 'liga';
+}

smppir-checkin-portal/public/index.html

+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
+    <meta name="theme-color" content="#000000">
+
+    <!-- Import Google Icon Font -->
+    <link href="./MaterialIcons.css" rel="stylesheet">
+    <!-- Import materialize.css -->
+    <link href="./materialize.min.css" rel="stylesheet">
+
+    <!--
+      manifest.json provides metadata used when your web app is added to the
+      homescreen on Android. See https://developers.google.com/web/fundamentals/engage-and-retain/web-app-manifest/
+    -->
+    <link rel="manifest" href="%PUBLIC_URL%/manifest.json">
+    <link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico">
+    <!--
+      Notice the use of %PUBLIC_URL% in the tags above.
+      It will be replaced with the URL of the `public` folder during the build.
+      Only files inside the `public` folder can be referenced from the HTML.
+
+      Unlike "/favicon.ico" or "favicon.ico", "%PUBLIC_URL%/favicon.ico" will
+      work correctly both with client-side routing and a non-root public URL.
+      Learn how to configure a non-root public URL by running `npm run build`.
+    -->
+    <title>Portal SMPPIR</title>
+  </head>
+  <body>
+    <noscript>
+      You need to enable JavaScript to run this app.
+    </noscript>
+    <div id="root"></div>
+    <!--
+      This HTML file is a template.
+      If you open it directly in the browser, you will see an empty page.
+
+      You can add webfonts, meta tags, or analytics to this file.
+      The build step will place the bundled scripts into the <body> tag.
+
+      To begin the development, run `npm start` or `yarn start`.
+      To create a production bundle, use `npm run build` or `yarn build`.
+    -->
+  <!-- Import jQuery before materialize.js -->
+	<script src="./jquery-2.1.1.min.js"></script>
+	<script src="./materialize.min.js"></script>
+	<!-- And then your bundled js -->
+	<!--<script src="path/to/your/bundle.js"></script>-->
+  <script defer="defer" src="//barra.brasil.gov.br/barra.js" type="text/javascript"></script>
+  </body>
+</html>