Lock node version to match targeted lambda env
Ran across this lock with checking an environment variable for undefined. In whatever node version my system has set as default, an environment variable that is undefined is set to the string undefined breaking a check. This should be revisited later, but for now, let's just lock the node version.
This commit is contained in:
parent
492a2faf9e
commit
49926de6f5
1 changed files with 1 additions and 0 deletions
1
.node-version
Normal file
1
.node-version
Normal file
|
@ -0,0 +1 @@
|
|||
6.10.3
|
Loading…
Reference in a new issue