Bump dependencies

[compulim]

Fixes #349.

Changelog

Changed

• Bumped dependencies, by @compulim, in PR #351
  • Production dependencies
    • @babel/runtime@7.14.8
    • botframework-streaming@4.14.1
    • buffer@6.0.3
    • core-js@3.15.2
    • cross-fetch@3.1.4
    • rxjs@5.5.12
    • url-search-params-polyfill@8.1.1
  • Development dependencies
    • @babel/cli@7.14.8
    • @babel/core@7.14.8
    • @babel/plugin-transform-runtime@7.14.5
    • @babel/preset-env@7.14.8
    • @babel/preset-typescript@7.14.5
    • @types/jest@26.0.24
    • @types/jsonwebtoken@8.5.4
    • @types/node@16.4.0
    • babel-loader@8.2.2
    • babel-jest@27.0.6
    • babel-plugin-istanbul@6.0.0
    • concurrently@6.2.0
    • dotenv@10.0.0
    • event-target-shim@6.0.2
    • get-port@5.1.1
    • global-agent@2.2.0
    • jest@27.0.6
    • jest-environment-jsdom@27.0.6
    • jsdom@16.6.0
    • nock@13.1.1
    • node-fetch@2.6.1
    • restify@8.5.1
    • rimraf@3.0.2
    • simple-update-in@2.2.0
    • typescript@4.3.5
    • webpack@5.45.1
    • webpack-cli@4.7.2
    • webpack-stats-plugin@1.0.3

Notably changes

• Production code change
  • DL ASE: Import Buffer from buffer package, instead of from global
• Non-production code change
  • Updated to jest@27
    • Jest is using Node.js test environment by default, instead of JSDOM, need to explicitly say the target environment
      • Node.js test environment means, no window object
      • Jest updated to jsdom@16
    • jsdom doesn't support Web Crypto
      • Tests that touch uuid will fail because lack of Web Crypto
      • We wrote a simple polyfill for jsdom in __tests__/setup/setupCrypto.js
    • When running under jsdom, pre-flighted CORS (i.e. OPTIONS + GET/POST) will continue to need Access-Control-Allow-Origin on the GET/POST, even though it has it in the OPTIONS response
      • We need to add Access-Control-Allow-Origin explicitly when running inside jsdom
      • Related to CORS Implementation  jsdom/jsdom#2024
    • Updated jest.config.js to transform packages that explicitly use ESM
      • Jest doesn't support ESM, but some packages (e.g. p-defer) explicitly enforce ESM thru { "type": "module" } in their package.json
    • Jest console log too much and Travis CI is killing Jest because of huge log size
      • Added --silent option to suppress console log when running npm test
  • Moved from .babelrc.js to babel.config.json for modernization
  • Updated to webpack@5
    • Moved from webpack-visualizer-plugin to webpack-stats-plugin
    • process.env.VERSION is never used in production code, removing it from DefinePlugin

Tested environment

• Unit tests via npm test
• Integration tests via directline.js (bundle)
  • Direct Line Web Socket
    • Edge
    • IE11
  • Direct Line App Service Extension
    • Edge
    • IE11
• Integration tests via tarball or npm link to Web Chat
  • Direct Line Web Socket
    • Edge
    • IE11
  • Direct Line App Service Extension
    • Edge
    • IE11

Integration tests consists of:

• Send/receive simple message
• Send/receive image attachment
  • Currently, due to an issue in Bot SDK, send/receive image attachment over DL ASE is not tested (https://github.com/microsoft/botbuilder-js/issues/3887)

For other browsers, we rely on Web Chat to test them.

Additional context

Jest doesn't like ESM

When running Jest with ESM-enforcing packages, such as p-defer, default Jest configuration will fail because it tries to import as ESM while running as CommonJS.

In addition to userland code, we also need to transpile /node_modules/p-defer while Jest is running Babel on-the-fly. Thus, transformIgnorePatterns is updated to include p-defer, which is used in test code.

    Details:

    /home/compulim/repos/BotFramework-DirectLineJS/node_modules/p-defer/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){export default function pDefer() {
                                                                                      ^^^^^^

    SyntaxError: Unexpected token 'export'

      2 |
      3 | import { createServer } from 'restify';
    > 4 | import createDeferred from 'p-defer';
        | ^
      5 | import getPort from 'get-port';
      6 |
      7 | export type PlaybackWithDeferred = {

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1479:14)
      at Object.<anonymous> (__tests__/setup/createServer.ts:4:1)

Transpiling on-the-fly

Both botframework-streaming and buffer package requires us to use babel-loader while bundling thru Webpack:

• botframework-streaming
  • It bundled itself (i.e. package.json/browser point to a monolithic bundle)
  • The bundle contains uuid and is not ES5-friendly, due to the use of default argument
• buffer
  • It contains code that is not ES5-friendly, due to the use of default argument