crandmck

Since `loopback-explorer` was renamed to `loopback-component-explorer` (see https://github.com/strongloop/loopback-component-explorer/issues/123), we need to propagate this change to the example apps; specifically the same changes made in https://github.com/strongloop/loopback-example-app/pull/79:

**1.** In `package.json`, change 

` "loopback-explorer": "^2.0.0",` to  `"loopback-component-explorer": "^2.1.0",`

**2.** In `server/component-config.json`, change 
```
{
  "loopback-explorer": {

crandmck

$ npm ls -g | grep strong-remoting
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/tar-fs/node_modules/tar-stream/node_modules/bl requires readable-stream@'~1.0.26' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/bower/node_modules/tar-fs/node_modules/tar-stream/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.0.33-1
npm WARN unmet dependency /usr/local/lib/node_modules/loopback-sdk-angular-cli/node_modules/express/node_modules/connect/node_modules/multiparty/node_modules/stream-counter requires readable-stream@'~1.1.8' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/loopback-sdk-angular-cli/node_modules/express/node_modules/connect/node_modules/multiparty/node_modules/readable-stream,
npm WARN unmet dependency which is version 1.1.13-1
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_modules/chalk requires strip-ansi@'^3.0.0' but will load
npm WARN unmet dependency /usr/local/lib/node_modules/npm/node_mod

crandmck

The Node Interactive conference in Portland kicked off yesterday with well-attended keynote talks from some prominent members of the Node community.

First off was James Snell from IBM, with a presentation titled "Convergence: Evolving Node.js with Open Governance and an Open Community." Snell is IBM's open technologies architect, and a member of the Node Core Technical Committee (CTC) and Technical Steering Committee (TSC). He observed that 2015 was an interesting year for Node, with the io.js fork generating some fear, doubt, and uncertainty.  Although there was a lot of excitement around Node, he said, there was a general belief that it could be better.

He noted that everyone was passionate about the technology, but there were profoundly different opinions about how project decisions were being made and the project was progressing. IBM, which started to embrace Node a few years ago, wanted to figure out how to help bring Node.js and io.js back together again to allow the project to continue to thrive, gro

crandmck

(base) ~/c2pa-js $rush install

Rush version 5.90.2 is not currently installed. Installing...
Trying to acquire lock for rush-5.90.2
Deleting old files from /Users/randmckinney/.rush/node-v16.13.0/rush-5.90.2

Running "npm install" in /Users/randmckinney/.rush/node-v16.13.0/rush-5.90.2
Successfully installed Rush version 5.90.2 in /Users/randmckinney/.rush/node-v16.13.0/rush-5.90.2.

Rush Multi-Project Build Tool 5.90.2 - https://rushjs.io