Skip to content
This repository has been archived by the owner on May 2, 2022. It is now read-only.

Update all npm #162

Merged
merged 18 commits into from
Jan 6, 2020
Merged

Update all npm #162

merged 18 commits into from
Jan 6, 2020

Conversation

jaredrethman
Copy link
Contributor

@jaredrethman jaredrethman commented Oct 14, 2019

Description of the Change

  • Updated all NPM dependencies.
  • CleanWebpackPlugin named export change. Requiring destructing at assignment in latest update.
  • Added module and process to .eslint globals.
  • Replaced .babel runtime config with bable.config.js.
  • These updates will require a minimum of Node v8.11:
    • This has been added to the README.md
    • Added .npmrc to enforce engine-strict. engineStrict via package.json property is deprecated and un-enforceable.
  • Added local property to testing.urls in package.json, resolving an error when running npm run test:a11y locally.

Alternate Designs

N/A

Benefits

Possible Drawbacks

  • NPM updates are on predominantly minor and patch versions. For package updates within major version updates, there are no breaking changes that would effect this code base (see below for list of these packages, and links, where possible, to release notes outlining breaking changes).

Verification Process

Screenshot 2019-10-14 at 20 38 28

  • I was able to verify through running all commands, and ensured the command line stayed free from any warnings/errors.

  • .npmrc to enforce engineStrict. engineStrict property via package.json is deprecated, since NPM 3.

Screenshot 2019-10-27 at 14 06 11

Checklist:

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my change.
  • All new and existing tests passed.

Applicable Issues

Style Lint:

Not an issue to this update, but applicable to why stylelint package, and associated packages, haven't been updated.

Screenshot 2019-10-27 at 03 00 53

Screenshot 2019-10-27 at 01 37 33

  • Below is the current list of outdated packages. The current stylelint* config, is the only configuration, which produces no warnings/errors.

Screenshot 2019-10-27 at 01 32 23

  • The below warning has been resolved.

Screenshot 2019-10-10 at 15 24 29

Major version changes:

Changelog Entry

  • Updated all npm packages.
  • Added local property to testing.urls in package.json, resolving an error when running npm run test:a11y locally.
  • Replaced .babelrc with babel.config.js
  • Updated CleanWebpackPlugin variable assignment, requiring destructing in the newer version.
  • Added .npmrc to enforce engineStrict

Associated Plugin Scaffold PR - 10up/plugin-scaffold#102

@timwright12
Copy link
Contributor

@jaredrethman can you add these to the plugin repo as well? Also, what's the benefit you see of moving babelrc?

@jaredrethman
Copy link
Contributor Author

jaredrethman commented Oct 15, 2019

@timwright12

can you add these to the plugin repo as well?

Definitely, I'll get on that asap.

what's the benefit you see of moving .babelrc

1.) Primary motivation: Babel >= 7 recommends babel.config.js over .babelrc. Future proofing.
2.) We can perform logical operations before deciding which presets/plugins to use i.e. NODE_ENV - #149

More here - https://babeljs.io/docs/en/config-files

@jaredrethman
Copy link
Contributor Author

@timwright12 have added this Code Review equivalent to the Plugin Scaffold - 10up/plugin-scaffold#102 and updated this pull.

package.json Show resolved Hide resolved
@timwright12
Copy link
Contributor

@jaredrethman looks like some conflicts popped up.

We'll need these updates for the plugin as well 10up/plugin-scaffold#102

One last note for Added module and process to .eslint globals. -- I don't see those in the updates in the .eslintrc file

@tylercherpak
Copy link
Contributor

@timwright12 given the nature of these changes, I think we should try to get them merged posthaste since it is very likely that these types of merge conflicts will keep coming up.

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
# Conflicts:
#	.eslintrc
#	package-lock.json
#	package.json
@jaredrethman
Copy link
Contributor Author

Hey @timwright12 ,

I have resolved those conflicts, updated 10up/plugin-scaffold#102 and added module & process to eslint global whitelist.

@timwright12
Copy link
Contributor

@jaredrethman looks good, just confirming the plugin repo before merge

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants