Code Monkey home page Code Monkey logo

medal-widget's Introduction

This project was bootstrapped with Create React App.

Modifications

File index.js has been modified to use the MedalWidget component as a widget rather than as a React app. In order to work on the comment with npm start uncomment the lines as instructed in that file.

To see how the component works as a widget start a web server in the build folder. The index.html file in that folder has been modified to initialize the component within the web page. For example:

cd build
python -m http.server

Note that recompiling the project with npm run build will overwrite the index.html file. To add the code that loads the widget simply add the following lines to index.html to the end of the body section:

  (...)

  <script type="text/javascript">
    window.MedalWidget.initialize('root', 'silver');
  </script>

</body>

Original README

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify

medal-widget's People

Watchers

 avatar  avatar

medal-widget's Issues

Reduce inode watcher usage

Hi! I’m a Internet traveler that just happened to land on your comment about the react watcher. I just wanted to ask if you were able to find a proper solution, since everybody else seems happy with just increasing the numbers of inode watchers. I observed that this repo has a total of 23 files and my number of watcher while executing it goes up by only 25, which seems to suggest that you indeed found the solution. I was able to monitor the number of watcher with

find /proc/*/fd -user "$USER" -lname anon_inode:inotify -printf '%hinfo/%f\n' 2>/dev/null \
| xargs cat \
| grep -c '^inotify'

Just to log my failed attempts, I tried to modify the ignored options on node_modules/webpack-dev-server/lib/Server.js:_watch() and node_modules/webpack/lib/node/NodeWatchFileSystem.js:watch() and there was no luck. I observed that by default the ignored option contains a RegEx with /^(?!\/my\/proyect\/path\/src\/).+\/node_modules\//g. That just adds to the confusion, since it should be ignoring everything on node_modules.

I’m sorry if this thread is out of place, I just wanted to give this a last try before accept that the Internet is being developed by millions of monkey brains.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.