Add backers and sponsors to homepage

[rickhanlonii]

Summary

This PR adds the Open Collective backers and sponsors to the home page. This is updated per deploy by running a fetchSupporters.js script which creates a backers.json file used during the deploy process (i.e the list is static instead of dynamic)

Screen

Note: FB Open Source included twice just for an example

[cpojer]

…aaaand we are back :D

[SimenB]

This seems to have broken node 6? Not sure how

[connectdotz]

hi, right now PRs are failing the ci/circleci: test-node-6 during yarn install, for example here:

[4/4] Building fresh packages...
error /home/circleci/jest/node_modules/jest-website: Command failed.
Exit code: 1
Command: node fetchSuporters.js
Arguments: 
Directory: /home/circleci/jest/node_modules/jest-website
Output:
/home/circleci/jest/website/fetchSuporters.js:23
          );
          ^

SyntaxError: Unexpected token )
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:549:28)
    at Object.Module._extensions..js (module.js:586:10)
    at Module.load (module.js:494:32)
    at tryModuleLoad (module.js:453:12)
    at Function.Module._load (module.js:445:3)
    at Module.runMain (module.js:611:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:160:9)

looks like @cpojer merged the change even with node-6 failure, does that mean that jest no longer support node-6? In that case should we just drop node-6 from ci test? or somebody from the jest-website can fix it? what is your recommendation for PRs now seeing this ci error? ignore? wait? or...?

[rickhanlonii]

@connectdotz it doesn't break node-6 support since that script is only for the website deploy, but we should fix since we may break node 6 without realizing it

[rickhanlonii]

Was fixed here: #6587

[connectdotz]

@rickhanlonii awesome! thx.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.