I dropped the plugin version in favor of the Github development version of Gutenberg. I removed the sup and sub text options from my Gutenberg plugin because they’re now included in the Core. Syncing all functionality between the dwp theme and dwp-guten plugin.
In the process of bringing this up to speed, I noticed that my system node –version kept taking over my default nvm –version. I generally go ahead and update my rvm versions of Node.js when this happens. After updating the version again, I got this notice about some of my global packages:
=> You currently have modules installed globally with `npm`. These will no
=> longer be linked to the active version of Node when you install a new node
=> with `nvm`; and they may (depending on how you construct your `$PATH`)
=> override the binaries of modules installed with `nvm`:
/Users/david/.nvm/versions/node/v10.16.3/lib
├── docsify-cli@4.4.1
├── gitbook-cli@2.3.2
├── grunt-cli@1.3.2
├── gulp-cli@2.2.0
├── npm-check-updates@4.1.1
├── sass@1.25.0
├── webpack@4.42.0
└── yarn@1.22.0
=> If you wish to uninstall them at a later point (or re-install them under your
=> `nvm` Nodes), you can remove them from the system Node as follows:
$ nvm use system
$ npm uninstall -g a_module
$david@macs?:~/sites/wp/app/themes/dwp(master⚡) » gulp scripts
Error: Missing binding /Users/david/Sites/wp/app/themes/dwp/node_modules/node-sass/vendor/darwin-x64-83/binding.node
Node Sass could not find a binding for your current environment: OS X 64-bit with Node.js 14.x
$david@macs?:~/sites/wp/app/themes/dwp(master⚡) » npm rebuild node-sass 1 ↵
rebuilt dependencies successfully
david@macs?:~/sites/wp/app/themes/dwp(master⚡) » gulp scripts 1 ↵
[06:24:10] Using gulpfile ~/Sites/wp/app/themes/dwp/gulpfile.js
[06:24:10] Starting 'scripts'...
? _Scripts
[06:24:10] Finished 'scripts' after 14 ms
david@macs?:~/sites/wp/app/themes/dwp(master⚡) »