Fixes #2748.

This PR will need to update CI pipeline.

Changelog Entry

Changed

• Resolves #2748, updated build scripts and CI pipeline, by @compulim, in PR #2767
• Bumped to [email protected], by @compulim in PR #2767

Description

• Decreased npm install time by about 4x
  • Do not install/build samples and embed
  • Down to ~7 packages to install
• npm start will start dev mode
  • Watch mode on all packages
  • Serve samples and bits (today, we need to run serve manually)
  • Instrumented build (i.e. bits good for both local dev and Docker tests)
• npm prepublishOnly will build production bits
• Support source maps for development build of CDN bundle
• Running 4 instances of Chrome (Azure CI seems using a D2-machine)
• Support test and code coverage reporting on VSTS

Design

For all packages, we provide 3 favors and 2 build scripts.

Favors

We offer 3 build favors:

Eval source maps took 1.6s to load in browser, while code without source maps only took 300-500ms to load. Thus, test build should not contains source maps to speed up testing in CI.

Tests run locally will be using development build without any code coverage collection.

To select different build favors, set node_env environment variable to:

• production
• test
• development or not set

Scripts

We offer 2 types of build processes:

• npm run build will build once
• npm start will build continuously with watch

Specific Changes

• Build
  • Remove samples from Lerna
    • Today, we no longer use npm link in samples, Lerna has no values in samples project
  • Update build script
    • npm run bootstrap will always use CI (CI = nuke + faster install)
    • npm run build to build once
    • npm start to build continuously
    • Remove clean and most scripts
    • npm test will target for development mode (watch, no coverage)
      • npm run test:ci will be used on VSTS (no watch, but coverage)
  • Renamed .babelrc to babel.config.json
  • Aggregated webpack*.config.js into a single webpack.config.js
    • Use node_env to determines build favor (development, production, testing)
  • Enabled source maps for development build
  • Clean up tsconfig.json, we are not using tsc to build, only use for type checking and emit declarations
    • Remove options that are related to build
  • Direct Line Speech converge to use the Web Chat config and scripts
• Code analysis
  • Added prettier.yml at root for prettifying babel-jest-config.js and other config files
• CI
  • Update .travis.yml to match VSTS
  • Preparing azure-pipelines.yml (we will tune and enable it after merged)
• Doc
  • Add BUILD_SCRIPTS.md for the build script design and verification
  • Add packages/README.md for explanation of different packages
  • Update CONTRIBUTING.md
• Test
  • Update .dockerignore to improve Docker build time
  • Enable Selenium Grid with 4 nodes
  • For port 5080, added an easy button to start Web Chat (we used to run main() in console)
  • Moved Jest config to separate jest.config.js file
  • Export JUnit test report and Cobertura code coverage report
  • Include Direct Line Speech tests in root npm test
  • Also serve directlinespeech.development.js with serve

To-do

• Rename .babelrc.js back to babel.config.json
  • Make sure to modify babel-jest-config.js
• Update /.github/CONTRIBUTING.md
• Clean up/packages/README.md
• Update Azure Pipelines

• Testing Added
  • This is build script changes, our current PR validation CI pipeline should be sufficient to test this PR.
  • However, since the build script is new, we should spare some time making sure daily builds are correct.