Interested in learning more about serverless AWS? Check out my Guide to Building with Serverless AWS
crow-api to show up on the site, so I went about refactoring it to meet the requirements. In order to become a part of the Construct Hub, a construct needs to be published on npm, use one of a list of specific licenses, contain specific keywords in the
package.json, and be compiled by JSII.
I mostly had
crow-api in the condition necessary to be included except for JSII compilation, which I purposefully avoided on my first pass. I wanted to get the code out the door quickly for my own use so I limited the amount of new technology I needed to learn (
crow-api was the first time I used the AWS CDK). This meant that I would need to learn JSII and Typescript but only enough to slightly refactor what I already had.
First thing was JSII and here are the commands I used to get it set up.
npm install --save-dev jsii-config npx jsii-config
Once I was able to convert everything over, there were a few more commands I ran to finish my work up and ship the new package.
npm install --save-dev jsii-build jsii-pacmak jsii-release npx jsii-build npx jsii-pacmak npx jsii-release
Of course, each has their own caveats.
jsii-build has its own set of rules and errors that popped up, which required me to write “better” Typescript to pass.
jsii-pacmak was fortunately straightforward after completing everything that
jsii-build yelled at me about.
jsii-release required me to create a PyPi account since it uses the account’s username and password to publish
pip packages, but I already had my npm registry credentials set up since that is where
crow-api lived beforehand.
Once my packages were published, I patiently waited for Construct Hub to pick them up. After a while, I realized that something was not right because nothing was showing up on their site. I made an issue on GitHub as noted in the contribution page’s FAQs. It turns out that my packages were missing an important piece: the
.jsii file. The issue has more details as to why that file was left out. Once I added it back in and republished,
crow-api popped up on Construct Hub 🎉
And that’s all. I didn’t use a cumbersome project management tool or anything else, just the
jsii by default so I will not have to worry about refactoring. My goal for
crow-api now is to write some tests for it and polish the Typescript. Since the construct is being advertised now on another channel, I feel it is my duty to write tests for the comfort and safety of its users and I knew I should have done that from the start. Polishing up the Typescript is just because I wanted to publish quickly and move the deeper Typescript learning phase to a later date.