serverless-export-env VS node-trekker

I recently published my serverless-exports-plugin for the Serverless Framework. While it shares similarities with existing plugins like serverless-export-env and serverless-export-outputs, my plugin supports to export both environment variables and stack outputs.

Afterward, when triggering npm run integration to start integration tests special Serverless Framework plugin (serverless-export-env) is connecting to the AWS account and saves locally in .awsenv file all Lambda's environment variables.

It looks like this plugin can help you: https://github.com/arabold/serverless-export-env

Currently both of the projects I still work on are CLI (command line interface) tools. I actually created them to help me build web applications faster. They are both generators, Which generate all of the crud routes for a Node.js api and crud routes and pages for Next.js. They still need a lot of work and are not generating production ready code yet. But I truly enjoy the time I spend working on them. I believe they will be really helpful to others one day, and that is really important to me.

I hope this short tutorial has been helpful, we have a basic functioning api and now have the knowledge to create more routes, models, and more. Again, I highly encourage you to check out the Node-Trekker documentation. This is a useful tool for somebody who might be starting out with NodeJS or just wants a quick api built for prototyping. This is not a feature packed tool, and will not generate perfect code for a production app. I highly encourage anyone interested in improving this app to make changes and submit a pull request.