StdLib Platform Updates: Logging, Node 8.2.1 Support, Slack Investment

Hey everyone! Keith from StdLib here. We’re super excited to announce the latest additions to StdLib. We’ve officially added logging as a first-class citizen of the platform (previously developers would have to use a third-party logging system). We’ve also updated the default Node engine to Node 8.2.1, meaning you get all the newest Node.js features and support out-of-the box. Finally, we’re thrilled to talk a little bit about our recent investment from Slack and where our roadmap is taking us.

Logging as a First-Class Citizen of StdLib

Logging Support

We’ve added logging support for all newly-deployed functions on our platform. Logs are very straightforward and intuitive to interface with. Let’s start with an imaginary user, westworldadmin. They’ve created a service calledmanage for managing WestWorld hosts, it’s running in a dev environment with a main function, a start and a shutdown function.

You would execute the associated functions using the StdLib command line tools with:

$ lib westworldadmin.manage[@dev]
> "Welcome to WestWorld Admin!"
$ lib westworldadmin.manage[@dev].start --host Dolores
"Some people choose to see the ugliness in this world..."
$ lib westworldadmin.manage[@dev].shutdown --host Maeve
Error: Host not responding

You can view the logs easily (please note, you’ll have to upgrade to the latest version) with:

$ lib logs westworldadmin.manage # shows all logs, all envs + fns
$ lib logs westworldadmin.manage[@dev]          # main fn logs
$ lib logs westworldadmin.manage[@dev].start    # start logs
$ lib logs westworldadmin.manage[@dev].shutdown # shutdown logs
$ lib logs westworldadmin.manage[@dev]*         # all dev fn logs

That’s it! It’s that easy. Logs during local testing will simply display in your console as you test.

Node 8.2.1 Support

Our main Node engine is now Node 8.2.1. You must use this engine to get logging support. To use a previous engine version, you should manually set "engine": "nodejs-8.0.0" in the "stdlib" field of your package.json.

Slack Investment

Happy to have Slack on board!

We’re also thrilled to announce Slack has joined us as an investor, we’re part of their newest batch of Slack Fund companies. We’re very thankful to have the support of the Slack team, and we’ll be working with them moving forward. We’ve already helped developers deploy well over 3,000 Slack Apps, and we plan to greatly increase that number moving forward. If you want to see how to get started with StdLib and Slack, check out our piece on how to build a Slack Bot in 9 Minutes with StdLib!

More to Come!

We’re actively building a lot more on the platform. Our goal, fundamentally, is to change the way we think about building software and deliver the best possible developer experience from novice to veteran engineers, and hopefully even students and newbies. You’ll be able to find us, in person, at the following events in the next couple of months:

• Confront, August 17th, Malmo, Sweden
• Functions2017, August 27th, Toronto, ON, Canada
• Slack Frontiers, September 11th — 12th, San Francisco, CA
• Serverlessconf NYC, October 8th — 11th, New York City, NY

Otherwise, please follow us on Twitter for updates, @StdLibHQ! You can also follow me for additional tidbits about what we’re doing and where we are, @keithwhor.