siri404-gh / sreeram.app_old Goto Github PK

View Code? Open in Web Editor NEW

1.0 2.0 0.0 2.92 MB

Boilerpalte, again!

Home Page: https://www.sreeram.app

License: MIT License

JavaScript 89.14% HTML 3.79% Dockerfile 1.27% Shell 4.21% CSS 1.59%

frontend boilerplate boilerplate-front-end react redux webpack4 bootstrap material-ui travis-ci unit-testing

sreeram.app_old's Introduction

Features

React
- React Hot Loader
- React router
- React Styleguide
- React native
Redux
- Redux thunk
- Redux middlewares
Material UI
Unit Testing
- Karma
- Jasmine
- Enzyme
Cross Browser testing
- Browserstack
Integration testing
- Cypress
Performance testing
- Lighthouse
Accessibility testing
- Pa11y
Build
- Webpack 4
  - Dev build
  - Prod build
  - Webpack Dev Server
  - Hot Module Replacement
  - SplitChunks
  - Sourcemaps
  - Visualizer
  - Workbox for PWA
  - Compression
  - HtmlWebpackPlugin
CI
- Travis CI
- Circle CI
- Gitlab CI
Retporting tools
- Codecov
- Coceclimate
- Codacy
- Sonarqube
- LGTM
- ImgBot
Deployment
- Heroku Node app deployment
- Heroku docker container deployment
- Heroku pipelines
- Firebase Hosting
- Firebase functions
Devops
- Docker
- Docker compose
SCM
- Git
- Github
- Gitlab
- Commitizen
- Commitlint
- Husky
- Lighthouse PR integration
Serverside
- Express
- Serverside Rendering
Tooling
- Eslint
- Editorconfig
Dependency Management
- Greenhouse Analytics
- Logrocket
- Airbrake
- Sentry
- Google Analytics

Environment variables

AIRBRAKE_ID
AIRBRAKE_PROJECT_KEY
BROWSERSTACK_TOKEN
BROWSERSTACK_USER
CODACY_PROJECT
CODACY_TOKEN
CODACY_USERNAME
CODECLIMATE_REPO_TOKEN
CODECOV_TOKEN
FIREBASE_TOKEN
HEROKU_API_KEY
HEROKU_APP_NAME
LIGHTHOUSE_API_KEY
LOGROCKET_ID
SENTRY_ID
SENTRY_TOKEN
SONAR_ORG
SONAR_TOKEN

npm scripts

npm build - Production build.
build:dev - Development build, without webpack-dev-server.
build:devserver - Development build, with webpack-dev-server.
test - Karma test.
lint:local - Eslint scan local.
commit - This is what you use to commit, not git commit.
docker - Builds the app in a dockerized container
lighthouse - Perform a lighthouse performance test.
lighthouse:pr - Travis invokes this for pull requests.
firebase:deploy - Deploy to firebase. Make sure you build first.
clean - Remove unnecessary folders.
sonar - Perform a sonar analysis. (You will need env variables set)
styleguide - Generate documentaton.
styleguide:eject - Generate and output documentation.
test:browserstack - Creates a tunnel to Browserstack and runs the unit tests in browsers specified in customLaunchers.js. (You will need env variables set)

Aim

One codebase for Desktop, Mobile, Android and Ios.
Focus on performance
Minimal footprint
Best practices
Performant

How it all works

Fork this repo.
Husky, Commitizen and Commitlint ensure that you follow good commit practices.
CircleCI and Travis perform the builds and deploys.
Every CircleCi build has 3 workflows and several stages like Lint, Test, Browserstack, Documentation, Build, Stage, Performance, Host etc.
Travis being slow, only performs a packaging build.
Lint - Performs a lint check.
Test - Performs unit testing and generates reports which are sent to Codecov, Codeclimate, Codacy and Sonarqube. (You will need to have signed up at all those places and set appropriate environment variables).
Browserstack - Runs the unit tests in browsers specified in customLaunchers.js. (You will need to have signed up and set appropriate environment variables).
Documentation - Generates react styleguide.
Build - Performs a build and generates a webpack visualizer analysis report.
Stage - Stages an app in Firebase (You will need to have signed up and set appropriate environment variables).
Performance - Generates 3 lighthouse performance test reports namely lighthouse, lighthouse2 and lighthouse3.
Host - Pushes the app to firebase. (You will need to have signed up and set appropriate environment variables).
Heroku - Deploys app to heroku (slower).

For more in depth understanding, go to https://www.sreeram.app

Examples:

Github Pages - https://sreeram.pro/sreeram.app
Test report - https://test.sreeram.app
Codecov report - https://codecov.sreeram.app
Codeclimate report - https://codeclimate.sreeram.app
Codacy report - https://codacy.sreeram.app
Sonar Analysis - https://sonar.sreeram.app
Bundle analysis - https://bundle.sreeram.app
Documentation - https://styleguide.sreeram.app
Performance report - https://lighthouse.sreeram.app
Stage app - https://sreeram-stage.firebaseapp.com
Heroku app - https://heroku-app.sreeram.app
Production app - https://www.sreeram.app

Others

Browserstack Cross browser automated testing.
Logrocket for monitoring
Airbrake for error catching.
Sentry for error catching.
Greenhouse Dependency management

Configuration

Replace app names in .firebaserc
Signup at all the places and set environment variables at CircleCI, Travis and Heroku.
Push the code.

sreeram.app_old's People

Contributors

Stargazers

Watchers

sreeram.app_old's Issues

An in-range update of webpack-manifest-plugin is breaking the build 🚨

The devDependency webpack-manifest-plugin was updated from `2.0.3` to `2.0.4`.

🚨 View failing branch.

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

webpack-manifest-plugin 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

✅ ci/circleci: stage: Your tests passed on CircleCI! (Details).
❌ ci/circleci: test: Your tests failed on CircleCI (Details).
✅ ci/circleci: heroku: Your tests passed on CircleCI! (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Commits

The new version differs by 5 commits.

bcca890 2.0.4
a6e8a2e doc: fix anchor link
5e1462b improve functions documentations
d35b413 upgrade dependencies
3aefada chore(package): upgrade to [email protected] (#163)

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

Version 3.5.0 of workbox-webpack-plugin was just published.

Branch	Build failing 🚨
Dependency	workbox-webpack-plugin
Current Version	3.4.1
Type	devDependency

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

workbox-webpack-plugin 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

✅ ci/circleci: stage: Your tests passed on CircleCI! (Details).
❌ ci/circleci: test: Your tests failed on CircleCI (Details).
✅ ci/circleci: heroku: Your tests passed on CircleCI! (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes

Workbox v3.5.0

🎉 What's New?

More customization when generating a service worker

Developers who use Workbox to generate their service worker (using the CLI, Node interface, or webpack plugin) can now take advantage of some additional options:

Setting offlineGoogleAnalytics: true will automatically add code to initialize Workbox's offline Google Analytics support in the generated service worker.
Both fetchOptions and matchOptions can now be used when configuring a runtimeCaching route, and those values will be passed through when constructing the corresponding Workbox caching strategy. Many thanks to @peterjosling for contributing this in #1608.
Using a custom plugin within a runtimeCaching route is now possible, thanks to enhancements made by @tsirlucas in #1598.

Here's a snippet of Workbox's build configuration, showing off all of the new features:

{
  // ... other options ...
  offlineGoogleAnalytics: true,
  runtimeCaching: {[
    urlPattern: /abc/,
    handler: 'staleWhileRevalidate',
    options: {
      fetchOptions: {
        mode: 'no-cors',
      },
      matchOptions: {
        ignoreSearch: true,
      },
      plugins: [{
        cacheDidUpdate: async ({cacheName, request, oldResponse, newResponse}) => {
          // Do something in your custom plugin.
        },
      }],
    },
  ]},
}

Support for the `PATCH` method in Workbox's router

Developers who need to match HTTP PATCH requests using Workbox's router can now do so, thanks to @kevin-brotcke's change in #1618.

Note that non-GET requests can't be added to a cache, so this is most useful when used alongside a network-only strategy configured with the Workbox background sync plugin, in order to retry failed PATCH requests once the network becomes available.

`workbox.core.registerQuotaErrorCallback` is now publicly visible

Due to a scoping error, the workbox.core.registerQuotaErrorCallback() function was previously not exposed. This is now public, matching the documented interface. Thanks to @Tronil for pointing out this discrepancy in #1616.

📖 Learn More

Check out our docs @ developers.google.com/web/tools/workbox/

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

The devDependency karma-webpack was updated from `3.0.4` to `3.0.5`.

🚨 View failing branch.

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

karma-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

❌ ci/circleci: test: Your tests failed on CircleCI (Details).
✅ ci/circleci: stage: Your tests passed on CircleCI! (Details).
✅ ci/circleci: heroku: Your tests passed on CircleCI! (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v3.0.5

2018-09-14

`Bug Fixes`

karma-webpack: handle multiple outputs correctly (#357) (59de62c)

Commits

The new version differs by 2 commits.

670f153 chore(release): 3.0.5
59de62c fix(karma-webpack): handle multiple outputs correctly (#357)

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

The dependency airbrake-js was updated from `1.4.6` to `1.4.7`.

🚨 View failing branch.

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

airbrake-js 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

❌ ci/circleci: heroku: CircleCI is running your tests (Details).
❌ ci/circleci: stage: CircleCI is running your tests (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
❌ ci/circleci: test: Your tests failed on CircleCI (Details).

Commits

The new version differs by 6 commits.

a5a0812 v1.4.7
57de7e7 Merge pull request #468 from airbrake/fix/promise-return-resp
250872f Return resp
f263d2b Update dependencies
cf5eb0d Merge pull request #467 from airbrake/fix/unhandled-rejection
80c6d37 Fix unhandled rejection when instrumenting fetch

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.3.6` to `4.3.7`.

🚨 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

✅ ci/circleci: stage: Your tests passed on CircleCI! (Details).
❌ ci/circleci: test: Your tests failed on CircleCI (Details).
✅ ci/circleci: heroku: Your tests passed on CircleCI! (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v4.3.7

Bug Fixes

babel 7 compatibility. #1043 (acad937)

Commits

The new version differs by 10 commits.

98fa7f5 chore(release): 4.3.7
d6e86a5 Merge pull request #1063 from gaearon/babel-7
acad937 fix: babel 7 compatibility. #1043
d6853b7 chore(readme): fix #1060, fix #1044
6b80a47 Merge pull request #1058 from Laassari/patch-1
2545905 Merge pull request #1062 from gaearon/fix-red-master
a30db75 Merge pull request #1059 from mshatikhin/master
ba46aba chore(build): fix react 16.4, #1061
80fb994 Typo in README
b9b185c change App's path in create-react-app

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 🌴

Setup Airbrake for your JavaScript application

Install Airbrake in 2 easy steps:

Step 1: Add the library
Include via CDN:

<script src="https://cdnjs.cloudflare.com/ajax/libs/airbrake-js/1.1.1/client.min.js"></script>

We also support installation via npm and Bower.

Step 2: Copy this config snippet to your app.js file

(You can find your project ID and API KEY with your project's settings):

var airbrake = new airbrakeJs.Client({
  projectId: <Your project ID>,
  projectKey: '<Your project API Key>'
});

To test that Airbrake has been installed correctly in your JavaScript project, just open up the JavaScript console in your internet browser and paste in:

airbrake.notify('hey there!')

Visit official GitHub repo for more info on alternative configurations and advanced options.

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

There have been updates to the react monorepoundefined

🚨 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

❌ ci/circleci: test: Your tests failed on CircleCI (Details).
✅ ci/circleci: heroku: Your tests passed on CircleCI! (Details).
✅ ci/circleci: stage: Your tests passed on CircleCI! (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes for v16.5.1

16.5.1 (September 13, 2018)

React

Improve the warning when React.forwardRef receives an unexpected number of arguments. (@andresroberto in #13636)

React DOM

Fix a regression in unstable exports used by React Native Web. (@aweary in #13598)
Fix a crash when component defines a method called isReactComponent. (@gaearon in #13608)
Fix a crash in development mode in IE9 when printing a warning. (@link-alex in #13620)
Provide a better error message when running react-dom/profiling with schedule/tracking. (@bvaughn in #13605)
If a ForwardRef component defines a displayName, use it in warnings. (@probablyup in #13615)

Schedule (Experimental)

Add a separate profiling entry point at schedule/tracking-profiling. (@bvaughn in #13605)

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

Version 7.3.7 of react-styleguidist was just published.

Branch	Build failing 🚨
Dependency	react-styleguidist
Current Version	7.3.6
Type	devDependency

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

react-styleguidist 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

❌ ci/circleci: test: Your tests failed on CircleCI (Details).
✅ ci/circleci: stage: Your tests passed on CircleCI! (Details).
✅ ci/circleci: heroku: Your tests passed on CircleCI! (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).

Release Notes

v7.3.7

Fixed: Add inline-scroll on props table (#1131)

Commits

The new version differs by 1 commits.

5263b27 Fix: Add inline-scroll on props table (#1131)

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

Version 7.15.0 of heroku was just published.

Branch	Build failing 🚨
Dependency	heroku
Current Version	7.14.4
Type	devDependency

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

heroku 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

❌ ci/circleci: heroku: CircleCI is running your tests (Details).
❌ ci/circleci: stage: CircleCI is running your tests (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
❌ ci/circleci: test: Your tests failed on CircleCI (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 logrocket is breaking the build 🚨

The dependency logrocket was updated from `0.6.16` to `0.6.17`.

🚨 View failing branch.

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

logrocket 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

❌ ci/circleci: stage: CircleCI is running your tests (Details).
❌ ci/circleci: heroku: CircleCI is running your tests (Details).
❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
❌ ci/circleci: test: Your tests failed on CircleCI (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 webpack is breaking the build 🚨

Version 4.17.3 of webpack was just published.

Branch	Build failing 🚨
Dependency	webpack
Current Version	4.17.2
Type	devDependency

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

✅ ci/circleci: stage: Your tests passed on CircleCI! (Details).
✅ ci/circleci: heroku: Your tests passed on CircleCI! (Details).
✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
❌ ci/circleci: test: Your tests failed on CircleCI (Details).

Release Notes

v4.17.3

Bugfixes

Fix exit code when multiple CLIs are installed
No longer recommend installing webpack-command, but still support it when installed

Commits

The new version differs by 7 commits.

ee27d36 4.17.3
4430524 Merge pull request #7966 from webpack/refactor-remove-webpack-command-from-clis
b717aad Show only webpack-cli in the list
c5eab67 Merge pull request #8001 from webpack/bugfix/exit-code
943aa6b Fix exit code when multiple CLIs are installed
691cc94 Spelling
898462d refactor: remove webpack-command from CLIs

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 🌴

siri404-gh / sreeram.app_old Goto Github PK

sreeram.app_old's Introduction

Features

Environment variables

npm scripts

Aim

How it all works

Examples:

Others

Configuration

sreeram.app_old's People

Contributors

Stargazers

Watchers

sreeram.app_old's Issues

The devDependency webpack-manifest-plugin was updated from 2.0.3 to 2.0.4.

Version 3.5.0 of workbox-webpack-plugin was just published.

🎉 What's New?

More customization when generating a service worker

Support for the PATCH method in Workbox's router

workbox.core.registerQuotaErrorCallback is now publicly visible

📖 Learn More

The devDependency karma-webpack was updated from 3.0.4 to 3.0.5.

Bug Fixes

The dependency airbrake-js was updated from 1.4.6 to 1.4.7.

The devDependency react-hot-loader was updated from 4.3.6 to 4.3.7.

Bug Fixes

Install Airbrake in 2 easy steps:

There have been updates to the react monorepoundefined

16.5.1 (September 13, 2018)

React

React DOM

Schedule (Experimental)

Version 7.3.7 of react-styleguidist was just published.

Version 7.15.0 of heroku was just published.

The dependency logrocket was updated from 0.6.16 to 0.6.17.

Version 4.17.3 of webpack was just published.

Bugfixes

Recommend Projects

Recommend Topics

Recommend Org

The devDependency webpack-manifest-plugin was updated from `2.0.3` to `2.0.4`.

Support for the `PATCH` method in Workbox's router

`workbox.core.registerQuotaErrorCallback` is now publicly visible

The devDependency karma-webpack was updated from `3.0.4` to `3.0.5`.

`Bug Fixes`

The dependency airbrake-js was updated from `1.4.6` to `1.4.7`.

The devDependency react-hot-loader was updated from `4.3.6` to `4.3.7`.

The dependency logrocket was updated from `0.6.16` to `0.6.17`.