v2.0.0

v2.0.0 Release

Release notes

This release is mainly focused around porting the source code to TypeScript. While the bulk of the functionality should remain the same, some of the internal structuring, naming, etc. has been changed to support our standard TS conventions as an organization.

Notable changes:

• All modules were capitalized to follow our standard convention with utility classes (CoreUtils, CollectionUtils, etc.). So any plugin projects or older branches referencing them will need to be updated. (old: testUtils -> new: TestUtils)
• All modules are now exported from an index file so consumers don't have to dive into the internal structure of the package to get modules
• All exports are now named exports, and will need to be referenced as a 'destructured' require if being used in a standard node project
  • Old: const dotnet = require("and-cli/modules/dotnet");
  • New: either const { Dotnet } = require("and-cli"); or with ES6-style imports: import { Dotnet } from "and-cli";
• While developing, it'll be the smoothest experience to run the watch npm script as the and-cli-dev alias now points to <repo>/dist/and-cli.js. We opted not to use ts-node due to its slowness/complications noted in PR #130

Known issues

#14 Investigate feasibility/benefit of porting project to Typescript
#145 Node 14 warnings "non existent property"

Contributors

@brandongregoryscott

Special thanks to these people for additional testing effort:
@wintondeshong
@Stefanie899
@myty
@nhinhdao