plastikfan / aergia-cli-ts Goto Github PK

fix deps to resolve vulns. Also, non eof the interface types should be exported. Clients should now rely on xiberia for interface types. The types in aergia that should be exported should be the implementation types only.

The files property in package.json should be crafted carefully. We don't really want to include everything in the 'dist' folder.

This could be quite a bg change. We need to ensure that all references to interface types are to xiberia (apart from internal interface types).

It was found (after mainy failed attempts) that this error can be mitigated by defining all the xiberia definitions in a local file rather than import from external module (and I mean external to be in a different npm package). So for now, the local xiberia file has to be kept in sync with the 'extrenal' xiberia package. Why this is an issue for aergia-cli-ts and it is not an issue for zenobia-ts is a big mystery, but does not need to be a show stopper for now.

Create boilderplate content

• Add boilderplate to package.json
• Create boilderplate source files
• Add boilderplate webpack source

index.js is in wrong location and needs to be moved to root dir. Also update references in package.json and webpack.onfg.js.

xiberia api has been refactored with breaking changes. Import these changes; see plastikfan/xiberia#11 for more details

branch: xiberia-api-refactored

The devDependency sinon was updated from 8.0.4 to 8.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Add new boiler plate from zenobia-ts

• Add dependency badges
• Add commitzen badge
• Add new typescript configs
• Add new webpack configs
• Check mocha config
• Add appropriate devDependencies

Currently, options defined on a command are catered for, but you can define options that are not tied to a command. IE if you want to define a cli with options at the top level, ie not command options, then this is not currently implemented.

branch: none-command-options

Copy the setup from eslint

• Define synchronous file load function
• Create synchronous load tests
• Define async file load fucntion
• Create async load tests

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency ts-node was updated from 8.9.1 to 8.10.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ts-node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

• Define composeCommand function for yargs
• Create tests for yargs composeCommand

branch: build-all-commands

• Define composeAllCommands function for yargs
• Create tests for yargs composeAllCommands
• Schema is a mandatory paramter, so it should be the first one, before any optional handler(s)
• Define handlers object, to contain option/comand/fail handlers
• Add replace option handler in ctor, with the handlers object
• Move the word 'Default' from IDefaultAeYargsOptionHandler to IAeYargsOptionCallback

Need to be able to set the default command. One of the commands should be allowed to be decorated with a 'default' attribute. When this comand is built, it should be configured as the default.

branch: default-command

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The dependency @types/ramda was updated from 0.27.4 to 0.27.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/ramda is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴