v3.0.3

• Remove node_modules/ip package. (@marcoandre1)

  NPM IP package vulnerable to Server-Side Request Forgery (SSRF) attacks :
  An issue in all published versions of the NPM package ip allows an attacker to execute arbitrary code and obtain sensitive information via the isPublic() function. This can lead to potential Server-Side Request Forgery (SSRF) attacks. The core issue is the function's failure to accurately distinguish between public and private IP addresses.

v3.0.2

• Update Footer.jsx. (@marcoandre1)

• Bump postcss-cli and override @svgr/webpack from react-scripts. (@marcoandre1)

  Implemented the answer for the issue Vulnerabilities... #13337 from create-react-app on GitHub.
  Like stated on the npm Docs :
  Overrides provide a way to replace a package in your dependency tree with another version, or another package entirely. These changes can be scoped as specific or as vague as desired.

• Run npm audit --fix. (@marcoandre1)

• Adds overrides for resolve-url-loader. (@marcoandre1)

• Bump gh-pages and yaml release pipeline. (@marcoandre1)

• Bump tailwindcss. (@marcoandre1)

v3.0.1

• Refactor components name. (@marcoandre1)
• Update Tailwind CSS to latest. (@marcoandre1)
• Add some Tailwind style. (@marcoandre1)

v3.0.0

• Upgrade to React 18 (@marcoandre1)

  To install the latest version of React:
  npm install react react-dom

  NOTE: see commit details Bump react react-dom

• Fix #162 [BUG]: hydrateRoot(...): Target container is not a DOM element. Particular attention to the parameters inversion in the NEW hydrate function: hydrate(<App tab="home" />, container) vs hydrateRoot(container, <App tab="home" />). (@marcoandre1)

  Extract from How to Upgrade to React 18:

  Finally, if your app uses server-side rendering with hydration, upgrade hydrate to hydrateRoot:

  // Before
  import { hydrate } from 'react-dom';
  const container = document.getElementById('app');
  hydrate(<App tab="home" />, container);
  
  // After
  import { hydrateRoot } from 'react-dom/client';
  const container = document.getElementById('app');
  const root = hydrateRoot(container, <App tab="home" />);
  // Unlike with createRoot, you don't need a separate root.render() call here.

• Upgrade to React Router v6 (@marcoandre1)

  Upgrade all <Switch> elements to <Routes>.
  <Route exact> is gone.
  <Route element> replaces <Route render> props. (see Upgrade to React Router v5.1)
  useParams inside your route component retrieves params. (see Upgrade to React Router v5.1)

  NOTE: see commit details Bump react-router-dom to v6

• Upgrade to react-redux 8 (@marcoandre1)

  Add useSelector() hook
  Allows you to extract data from the Redux store state, using a selector function.
  The selector is approximately equivalent to the mapStateToProps argument to connect conceptually.

  NOTE: I had to change to useSelector() in the Dashboard component instead of mapStateToProps() because of the upgrade to React router v6. See commit details Add useSelector hook

• Bump @headlessui/react because previous version incompatible with React 18. (@marcoandre1)

v2.0.5

• Add "puppeteerArgs": ["--no-sandbox", "--disable-setuid-sandbox"] in package.json as recommended in README:

  Puppeteer (Headless Chrome) may fail due to sandboxing issues. To get around this, you may use:
  "puppeteerArgs": ["--no-sandbox", "--disable-setuid-sandbox"]
  Read more about puppeteer troubleshooting.

• Set ubuntu-latest in Github Actions workflow. The proposed puppeteer fix should fix the issue: There is a phenomenon in which the build does not end in the GitHub Actions (Linux Latest) environment.

v2.0.4

• Fix #147 language switch button closes correctly when language is choose (@marcoandre1)
• Fix burger menu for mobile: closes when link is selected (@marcoandre1)

v2.0.3

• PR #149
  • Bump app version from v2.0.2 to v2.0.3 (@marcoandre1)
  • Fixe #146 Add badge status to README (@marcoandre1)
  • Bump react-snap-test version from v1.23.6 to v1.23.8: fix #148 Bumb puppeteer in react-snap dependency (@marcoandre1)

v2.0.2

• #77 Add project link to images: PR #142 (@marcoandre1)

v2.0.1

v2.0.1

• #78 Add new projects: actually some old projects that where never included on the website (@marcoandre1)
• #131 Add GitHub Actions for automatic deployment: take a look at .github/workflows/release-on-master-pr.yml file for more info. (@marcoandre1)
• #108 Problem with deployments: see PR #132 Update gh-pages dependency from 2.2.0 to 4.0.0 and #134 Add GitHub action for automatics deployment. After some fixes on the workflow file, everything seems to run smoothly.

v2.0.0

• #109 Add a deployment log instead of putting info in the README (@marcoandre1)
• #110 Add issue and pull request templates (@marcoandre1)
• #79 Dependency updates: #96 Update CRA from 5.0.0 to 5.0.1, #104/#99/#96 Update react-snap 1.23.0 to react-snap-test 1.23.6 (@marcoandre1)

NOTE: all security vulnerabilities from react-snap have been removed! Only 6 high vulnerabilities left from CRA. No fix yet. But seems to be a false alarm.

December 2021 UPDATE: Updated Create React App from v4.0.1 to v5.0.0:

npm install --save --save-exact [email protected]

Everything went smooth but my svg files wouldn't load. I solved it by running an online optimizer on my svg files (https://www.svgviewer.dev/).

NOTE: while trying to fix npm warnings I found this issue: Help, npm audit says I have a vulnerability in react-scripts!. As of December 2021, I have some warnings (3 low and 18 moderate) on npm install and it seems to be a problem with the new CRA release using old libraries (and probably because react-snap isn't mantained since December 13, 2018). There is no fix yet.