Cloud Game Lister

Cloud Gaming Lister is a Chrome extension used for GEFORCE NOW support for Steam games.

Setup

Before the run this project, install it locally using npm:

$ npm install

Development

To run this project on development mode:

$ npm run dev

Build

To build this project on production mode:

$ npm run build

Installation

To use this extension, please install it from the Chrome Web Store.

Features

• All supported Steam games list for "GEFORCE NOW"
• Allows you to see new supported games (in popup and in extension game list page)
• Allows you to see and filter all supported steam games on the extension game list page (link in the popup)
• Allows you to see "GEFORCE NOW" support on the steam pages
  • Main page
  • Search pages
  • Game detail page
  • Bundle Detail
  • Tags pages
  • Genre pages
  • Category pages
  • Explore new page
  • Special Offers page
  • Sale pages
  • VR page
  • Friend Activity page
  • Followed Games page
  • User Games page (custom url) (tabs: recent, all, perfect)
  • User Games page (profile id) (tabs: recent, all, perfect)
  • Curators page
  • Curator Detail page
  • Community Recommendations page
  • Franchise page
  • Developer page
• Allows you to see new games in popup page
• Desktop notifications for new game(s) (optional)

Please read this section before start to development.

First of all you have to install these plugins to your editor (vscode), but if you are using an another code editor or IDE install them for your dev environment

• ESLint Plugin for VS Code

• Prettier - Code formatter for VS Code

• EditorConfig for VS Code

If you don't use one of these Code Editor/IDE please check is your EDITOR/IDE exist or not please install Editor Config plugin for your Code Editor/IDE.

Linter / Commit Messages

While developing this library you should take an attention to linter rules, all of your codes and commit messages, because you can't do any development without checking by rules.

Notice: Before commit to changes, HuskyJs checking these commit messages / linter rules

If you get a lint's error when you commiting a message, you can check for eslint linter rules or if you get an error because of your commit message you can check below commit message types and examples or you can check from Conventional Commits.

Commit-lint Types

Examples:

git commit -m "feat: navbar component added"

git commit -m "docs(readme): server link added"

• build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
• ci: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
• chore: Updating packages,build project etc. (no production code change)
• docs: Documentation only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that neither fixes a bug nor adds a feature, when refactoring a production code, eg. renaming a variable.
• revert: A commit revert message
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

Contributing

You may contribute to this project by opening an issue to file a bug report or feature request. If you would like to contribute code, please open an issue explaining what you're changing and submit a pull request.

Privacy Policy

This extension requires permissions for "storage" and "notifications"

Contributors ✨

Thanks goes to these wonderful people (emoji key):

Emre Sandikci 💻 🤔 🚧 👀

Demir Yasin Oruc 💻 🤔 🚧 👀

Arda Fidancı 💻 🌍

This project follows the all-contributors specification. Contributions of any kind welcome!