GithubHelp home page GithubHelp logo

rwieruch / visual-regression-testing-react-storybook Goto Github PK

View Code? Open in Web Editor NEW
27.0 4.0 15.0 10.14 MB

Visual Regression Testing in React with Storybook

Home Page: https://www.robinwieruch.de/visual-regression-testing-react-storybook

JavaScript 100.00%
react reactjs visual-regression-testing visual-regression-tests react-storybook react-storybook-addons

visual-regression-testing-react-storybook's Introduction

visual-regression-testing-react-storybook

Build Status Coverage Status Slack Greenkeeper badge

A React application which implements visual regression tests by using Jest and React Storybook. Read more about it: Visual Regression Testing and React Storybook

Features

  • React 16
  • Webpack 4
  • Babel
  • Staging ES Next Features
  • Hot Module Replacement
  • Testing
    • Mocha
    • Chai
    • Enzyme
    • Sinon
    • Jest
    • Unit/Integratio Test (Chai, Enzyme) Watcher
    • Snapshot Test (Jest) Watcher
    • Travis CI
    • Coveralls.io
  • Storybook 4
    • Knobs
    • Actions
    • Storyshots
    • Imageshots
    • Viewport

Installation

  • git clone [email protected]:rwieruch/visual-regression-testing-react-storybook.git
  • cd visual-regression-testing-react-storybook
  • npm install
  • npm start
  • visit http://localhost:8080/

Running Storybook

  • npm run storybook

Running Visual Regression Tests

  • npm run storybook
  • npm run test:snapshot

visual-regression-testing-react-storybook's People

Contributors

greenkeeper[bot] avatar rwieruch avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar

Forkers

gevara12 palianah houkah2690 zifkage yogitaunay osynaptony jayk19 uxnivek adamkeinan elizaschwartz nigam-ashish ashishnigam miriampancorbo2 muthuvijay lzhgostudy

visual-regression-testing-react-storybook's Issues

An in-range update of babel-loader is breaking the build 🚨

The devDependency babel-loader was updated from 8.0.4 to 8.0.5.

🚨 View failing branch.

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

babel-loader 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).
Release Notes for 8.0.5
  • Update find-cache-dir to 2.0
Commits

The new version differs by 8 commits.

  • 20c9e0e 8.0.5
  • de51b5d chore: Update ava
  • 66f92af Remove docs mention about sourceMap option being ignored (#750)
  • 6df8af1 Update dependencies and run all tests (#745)
  • 2c61de5 Add node 11 and 10 (#744)
  • 1bda840 Fix config issue in example (#708)
  • 364387d Merge pull request #698 from MattGurneyAMP/patch-1
  • 98f936d Fix license header and link

See the full diff

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 storybook is breaking the build 🚨

There have been updates to the storybook monorepo:

🚨 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 storybook group definition.

storybook 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).
Commits

The new version differs by 10 commits.

  • 0cc22e4 v4.0.4
  • 9c2aa19 4.0.4 changelog
  • 3535baa Merge pull request #4654 from storybooks/dependabot/npm_and_yarn/react-syntax-highlighter-10.0.0
  • c11a3e0 Merge pull request #4705 from storybooks/fix-deps
  • 7eca652 Merge pull request #4708 from dumbNickname/mjs-support
  • ca54817 Merge pull request #4715 from cfleschhut/docs/add_auth0_cosmos_to_examples
  • da8cd05 Merge pull request #4669 from tarikhamilton/knobs/number-proptypes-bug
  • 9ebbce7 Merge pull request #4683 from storybooks/addon-jest/fix-configureviewport
  • 4bbc479 Merge pull request #4689 from storybooks/addon-jest/fix-tests-matching
  • 9a70c94 Merge pull request #4720 from storybooks/node-11-fix

See the full diff

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 all 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 delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all 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 delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

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

There have been updates to the react monorepo:

    • The dependency react was updated from 16.6.3 to 16.7.0.

🚨 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 react group definition.

react 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).
Release Notes for v16.7.0

React DOM

Scheduler (Experimental)

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 webpack-cli is breaking the build 🚨

The devDependency webpack-cli was updated from 3.1.2 to 3.2.0.

🚨 View failing branch.

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

webpack-cli 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).
Commits

The new version differs by 124 commits.

  • 6253a73 chore: v.3.2.0
  • 0c3be76 chore: make tests pass
  • 0b6bab3 chore: better defaults
  • 78436ff chore: add-on -> scaffold
  • 3281372 chore: simplify clean-all script
  • b0f4a0f chore: addon -> scaffold
  • 82c9ea8 chore: update lockfiles
  • a3fe013 Merge pull request #716 from EvsChen/dist-scaffold
  • f9bb82d Merge pull request #693 from lakatostamas/feature/find-config-recursively
  • 3ec2e9d chore: resolve conflict
  • 83602d4 chore: update package lock and scripts
  • d82b016 Merge pull request #720 from rishabh3112/patch-7
  • 4d9c847 Merge pull request #723 from eavichay/patch-1
  • 4b2a127 docs: improve the docs (#722)
  • 9ad8c1d See #721

There are 124 commits in total.

See the full diff

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 jsdom is breaking the build 🚨

The devDependency jsdom was updated from 13.0.0 to 13.1.0.

🚨 View failing branch.

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

jsdom 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).
Commits

The new version differs by 35 commits.

  • 26f0bed Version 13.1.0
  • 91b10c3 Support setting custom validity messages on
  • 172d587 Update webidl2js
  • e862f4a Run activation behavior hooks from the event dispatch algorithm
  • 39c4c23 Update dependencies
  • cfc4786 Set the composed flag for FocusEvent
  • b4c04db Correctly reflect
      's start property with default value
    1. 7e66dfb Support 's htmlFor property
    2. ce8e8c6 Support setting custom validity messages on
    3. 4f783c6 Remove unused feature methods
    4. 2341bbe Revert "Add preliminary support for <iframe srcdoc>"
    5. 7107df6 Add preliminary support for <iframe srcdoc>
    6. b2c5358 Fix getter for <title>'s text property
    7. c7688ab Add and support SVGTitleElement in document.title
    8. 0d8e263 Add namespace argument for traversal helpers

There are 35 commits in total.

See the full diff

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 react-hot-loader is breaking the build 🚨

The devDependency react-hot-loader was updated from 4.5.3 to 4.6.0.

🚨 View failing branch.

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

react-hot-loader 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).
Release Notes for Know your Errors

Features

  • implement flexible error boundaries (1846019)
  • new root/hot API for better error management. Fixes #1078, #1111 (3029428)
Commits

The new version differs by 24 commits.

There are 24 commits in total.

See the full diff

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 coveralls is breaking the build 🚨

The devDependency coveralls was updated from 3.0.2 to 3.0.3.

🚨 View failing branch.

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

coveralls 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).
Release Notes for Dependency security updates

As suggested by NPM and Snyk.

Commits

The new version differs by 1 commits.

  • aa2519c dependency security audit fixes from npm & snyk (#210)

See the full diff

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 enzyme is breaking the build 🚨

There have been updates to the enzyme monorepo:

    • The devDependency enzyme was updated from 3.7.0 to 3.8.0.

🚨 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 enzyme group definition.

enzyme 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 🌴

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

There have been updates to the enzyme monorepo:

🚨 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 enzyme group definition.

enzyme 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 🌴

An in-range update of start-server-and-test is breaking the build 🚨

The devDependency start-server-and-test was updated from 1.9.1 to 1.9.2.

🚨 View failing branch.

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

start-server-and-test 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 failed (Details).
Release Notes for v1.9.2

1.9.2 (2019-08-05)

Bug Fixes

  • deps: update dependency wait-on to v3.3.0 (#187) (de9e7b6)
Commits

The new version differs by 2 commits.

  • de9e7b6 fix(deps): update dependency wait-on to v3.3.0 (#187)
  • 542a44e chore(deps): update dependency dependency-check to v3.4.1

See the full diff

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 cypress is breaking the build 🚨

The devDependency cypress was updated from 3.1.2 to 3.1.3.

🚨 View failing branch.

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

cypress 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 🌴

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

There have been updates to the storybook monorepo:

🚨 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 storybook group definition.

storybook 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).
Release Notes for v4.0.10

Fixes 4.0.9

Bug Fixes

  • Core: Use correct cache directory path (#4792)
  • Addon-Info: fix docgen description display (#4685)
  • Addon-storyshots-puppeteer: fix peerDependencies (#4828)
Commits

The new version differs by 10 commits.

  • c6de649 v4.0.10
  • 45b7945 4.0.10 changelog
  • ee957e3 Merge pull request #4884 from stevehanson/patch-2
  • a0a67e2 Remove unnecessary instruction
  • e68a4f8 Clarify Typescript instructions for config.ts
  • fae0ff5 Revert "cache DLL"
  • 2bd8540 cache DLL
  • 5c7f0c3 Fix failing snapshot test
  • abe699c Fix dirty lock file
  • 155283b Merge pull request #4838 from storybooks/core/fix-mangle

See the full diff

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 sinon is breaking the build 🚨

The devDependency sinon was updated from 7.3.1 to 7.3.2.

🚨 View failing branch.

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

sinon 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).
Commits

The new version differs by 6 commits.

  • 15a9d65 Update docs/changelog.md and set new release id in docs/_config.yml
  • 5d770e0 Add release documentation for v7.3.2
  • 585a1e9 7.3.2
  • b51901d Update CHANGELOG.md and AUTHORS for new release
  • 83861a7 Update Lolex to bring in fix for sinonjs/lolex#232
  • 2430fd9 Documentation (#2004)

See the full diff

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/core was updated from 7.2.0 to 7.2.2.

🚨 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 🌴

An in-range update of @storybook/addon-storyshots-puppeteer is breaking the build 🚨

The devDependency @storybook/addon-storyshots-puppeteer was updated from 4.0.9 to 4.0.10.

🚨 View failing branch.

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

@storybook/addon-storyshots-puppeteer 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).
Release Notes for v4.0.10

Fixes 4.0.9

Bug Fixes

  • Core: Use correct cache directory path (#4792)
  • Addon-Info: fix docgen description display (#4685)
  • Addon-storyshots-puppeteer: fix peerDependencies (#4828)
Commits

The new version differs by 10 commits.

  • c6de649 v4.0.10
  • 45b7945 4.0.10 changelog
  • ee957e3 Merge pull request #4884 from stevehanson/patch-2
  • a0a67e2 Remove unnecessary instruction
  • e68a4f8 Clarify Typescript instructions for config.ts
  • fae0ff5 Revert "cache DLL"
  • 2bd8540 cache DLL
  • 5c7f0c3 Fix failing snapshot test
  • abe699c Fix dirty lock file
  • 155283b Merge pull request #4838 from storybooks/core/fix-mangle

See the full diff

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 webpack is breaking the build 🚨

The devDependency webpack was updated from 4.26.1 to 4.27.0.

🚨 View failing branch.

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

webpack 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).
Release Notes for v4.27.0

Features

  • When using functions as plugins they are now also called with the compiler as parameter
    • This make it possible to use arrow functions as plugins
  • splitChunks.maxSize now emits a warning when minSize > maxSize
  • Loaders have now access to a getResolve method to create their own resolver function with custom options

Bugfixes

  • splitChunks.cacheGroups.xxx.enforce now behaves as documented and enforce chunk creation
  • splitChunks.cacheGroups.xxx.enforce now no longer deletes minSize for maxSize
  • fixes a bug where splitChunks cause cacheGroups to be incorrectly merged when using the same name
    • now conditions are considered per cacheGroup
    • the correct cache group comment is displayed in stats
  • fixes a bug which causes providedExports not to be updated on rebuilds when using export * from
Commits

The new version differs by 12 commits.

  • f47bf8b 4.27.0
  • a67ffcd Merge pull request #8452 from webpack/feature/resolveWithOptions
  • 96f625c Merge pull request #8457 from webpack/bugfix/rebuild-provided-exports
  • 56feccc convert test case to normal function for node.js 6 support
  • 2f4296e fix a bug which causes incorrect providedExports for cached modules
  • f944002 Merge pull request #8451 from webpack/bugfix/split-chunks
  • 162da1c add getResolve method to loader context
  • 3b46b48 enforce doesn't affect minSize for maxSize
  • 72a8a1f Merge pull request #8440 from Connormiha/oprimize-chunk-can-be-integrated
  • 537d3e4 Cache hasRunstime in chunk
  • e3e8a68 Merge pull request #8405 from xiaoxiaojx/fix-function-plugin-apply
  • 70b9a1b fix parameter missing when plugin type is a funtion

See the full diff

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 webpack-dev-server is breaking the build 🚨

The devDependency webpack-dev-server was updated from 3.1.10 to 3.1.11.

🚨 View failing branch.

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

webpack-dev-server 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).
Release Notes for v3.1.11

3.1.11 (2018-12-21)

Bug Fixes

Commits

The new version differs by 9 commits.

  • ff2874f chore(release): 3.1.11
  • b3217ca fix: check origin header for websocket connection (#1603)
  • 68dd49a fix: add url for compatibility with webpack@5 (#1598) (#1599)
  • fadae5d fix(Server): mime type for wasm in contentBase directory (#1575) (#1580)
  • 7a3a257 fix(package): update spdy v3.4.1...4.0.0 (assertion error) (#1491) (#1563)
  • 1fe82de ci(travis): Node 11 (on OS X) crashes, use 10 for now (#1588)
  • 55398b5 fix(bin/options): correct check for color support (options.color) (#1555)
  • 927a2b3 fix(Server): correct node version checks (#1543)
  • fa96a76 chore(PULL_REQUEST_TEMPLATE): allow features (#1539)

See the full diff

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 all 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 delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

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.