Updating npm to 16.20.2

[stephiescastle]

Checklist

• Include a description of your pull request and instructions for the reviewer to verify your work.
• Link to the issue if this PR is issue-specific.
• Create/update the corresponding story if this includes a UI component.
• Create/update documentation. If not included, tell us why.
• List the environments / browsers in which you tested your changes.
• Tests, linting, or other required checks are passing.
• PR has an informative and human-readable title
  • PR titles are used to generate the change log in releases; good ones make that easier to scan.
  • PRs will be broadly categorized in the change log, but for even easier scanning, consider prefixing with a component name or other useful categorization, e.g., "BaseButton: fix layout bug", or "Storybook: Update dependencies".
• PR has been tagged with a SemVer label and a general category label, or skip-changelog.
  • These tags are used to do the aforementioned broad categorization in the change log and determine what the next release's version number should be.
  • Release Drafter will attempt to do the category labeling for you! Please double-check its work.

Description

• Updates explorer-1 to npm v16.20.2.
• Also downgrades @tailwindcss/forms to 0.3.4 as the compatibility has changed (0.4.0+ requires Tailwind 3: https://github.com/tailwindlabs/tailwindcss-forms/releases?page=2)

Instructions to test

Tested in the following environments/browsers:

Operating System

• macOS
• iOS
• iPadOS
• Windows

Browser

• Chrome
• Firefox ESR
• Firefox
• Safari
• Edge

[stephiescastle]

Noting a dependency issue that I'll look into Monday:

 npm ERR! While resolving: @tailwindcss/forms@0.5.0
npm ERR! Found: tailwindcss@2.2.19
npm ERR! node_modules/tailwindcss
npm ERR!   tailwindcss@"^2.2.19" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer tailwindcss@">=3.0.0 || >= 3.0.0-alpha.1" from @tailwindcss/forms@0.5.0
npm ERR! node_modules/@tailwindcss/forms
npm ERR!   @tailwindcss/forms@"^0.5.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: tailwindcss@3.4.3
npm ERR! node_modules/tailwindcss
npm ERR!   peer tailwindcss@">=3.0.0 || >= 3.0.0-alpha.1" from @tailwindcss/forms@0.5.0
npm ERR!   node_modules/@tailwindcss/forms
npm ERR!     @tailwindcss/forms@"^0.5.0" from the root project
npm ERR! 

[stephiescastle]

Noting a dependency issue that I'll look into Monday

Now fixed.

[stephiescastle]

My comment markup is confusing, but what I intended to suggest was that another approach we took could be to just widen the compatibility instead of upgrading explorer-1:

    "node": "^14.19.0",
    "npm": "^6.14.16"

Note the addition of the carets rather than bumping version numbers.

I'm pro-upgrading but the suggestion above would be less disruptive for other projects that use explorer-1.

[Scotchester]

Dev page and Storybook are both working fine. While testing, I noticed that Placekitten has run out of lives 😿 so I standardized all of our placeholder images to use https://picsum.photos.

One thing I noticed is that after building for Storybook, the built CSS and JS had some minor changes. Think we should go ahead and include those?

My comment markup is confusing, but what I intended to suggest was that another approach we took could be to just widen the compatibility instead of upgrading explorer-1:

    "node": "^14.19.0",
    "npm": "^6.14.16"

Note the addition of the carets rather than bumping version numbers.

I'm pro-upgrading but the suggestion above would be less disruptive for other projects that use explorer-1.

I agree we should press on. 16 is already EOL, too, so this should just be considered a stepping stone to 18 and 20. As far as we know, our projects are the only ones that consume explorer-1, right? I don't feel bad about forcing our own projects to upgrade if they want to upgrade explorer-1.

[stephiescastle]

Thanks @Scotchester, I've updated the build files.