If you know me well then you probably know how in love I am with serverless backends, cloud functions, lambdas, and whatever other fancy names they can give for basically a pay-only-for-what-you-use server. I'm also pretty fond of the Serverless Framework (https://github.com/serverless/serverless) which let's you easily scaffold out a new project meant to be run on a serverless architecture. Although I've only been using it for AWS Lambda, I recently made a little mistake that turned out to be a great discovery, and in this post I'll tell you all about it!
0 Comments
Oh golly, I hope I don't end up being one of those bloggers that posts about Windows stuff all the time! Lol. It's true though- I recently started working at a bank where they are forcing everyone to use Windows 7 for NodeJs stuff! smh -_-
Aaaaaaaaaanyway, here's how you can kill all running node processes in the Windows cmd promt.
SOLVED: Angular 2 AOT "Error Encountered Resolving Symbol Salues Statically" With Ngrx ProvideStore2/28/2017
If you were using an older version of angular CLI before it had aot built into it then you may start to receive these errors when you run you usual `ng serve` or `ng build` commands:
ERROR in Error encountered resolving symbol values statically. Function calls are not supported. Consider replacing the function or lambda with a reference to an exported function (position 7:3 in the original .ts file), resolving symbol mainStoreReducer in /.../, resolving symbol AppModule in /../, resolving symbol AppModule in /../, resolving symbol AppModule in /../ I'm almost embarrassed to be admitting that I was Googling this today, but for some reason I am always forgetting the shortcut key to delete your current line in terminal. As a node.js enthusiast, vim user, and avid terminal user I often find myself hitting the up and down keys to cycle through my previous commands, but then I realize that I just want an empty line in the prompt so I can just type something. I hate sitting there mashing the backspace key and always thought to myself, "there must be a better way". This is that better way!
Yep, I got this example working today as an example for an upcoming talk I'm given about AWS Lambda. Here's the beautiful email in my inbox, sent from my AWS Lambda function:
|
AuthorThe posts on this site are written and maintained by Jim Lynch. About Jim...
Categories
All
Archives
March 2023
|