All environment variables are missing

[zamirdan]

This is a Bug Report

Description

All environment variables are missing.
I have built very simple project with only one function:
module.exports.hello = (event, context, callback) => {
const response = {
statusCode: 200,
body: JSON.stringify({
message: process.env.MY_VAR,
input: event,
}),
};

callback(null, response);
};

I have added to the yml file under provider this lines
environment:
MY_VAR: abc

when I run it without the plugin it works, but after I'm installing the plugin it doesn't.

Similar or dependent issue(s):

• Some, not all, environment vars are missing #99
  I'm using:
  serverless-webpack 4.0.0
  webpack 3.8.1
  serverless 1.24
  Windows 10

[HyperBrain]

Hi @zamirdan , thanks for raising the issue.

This is very strange. The plugin does not do anything with the environment variables and that should be handled completely by Serverless. Are the variables missing when you deploy the function, or only if you run the code locally? And which tool do you use to run them?

Can you post the complete serverless.yml, and the webpack config?

[zamirdan]

Thank you for the quick reply.
I am missing the environment variables in both situations (local and deploy).
I use "sls invoke function/local" to run my tests.

yml file:

service: testEnv

provider:
  name: aws
  runtime: nodejs6.10
  versionFunctions: false
  region: us-east-1
  environment:
    MY_VAR: abc

package:
  individually: true

functions:
  testEnv:
    handler: functions/testEnv.hendler

plugins:
  - serverless-webpack

[HyperBrain]

Can you try the same with one of the provided examples, preferrably https://github.com/serverless-heaven/serverless-webpack/tree/master/examples/serverless-offline or https://github.com/serverless-heaven/serverless-webpack/blob/master/examples/babel-dynamically-entries?
Just add an environment definition to the serverless.yml and print it in one of the functions? It looks to me that something with your function configuration is wrong, but it would be better to start from a known working example to find out, what exactly is wrong.

[zamirdan]

Hi,
Thank you, I have found the problem.
It was in the webpack.config.js file...
target: 'node' was missing.
I could pack deploy and invoke all functions without it, but it a must for environment variables.
Thanks

Note... I read the documentation again and it's a bit confusing...

[HyperBrain]

@zamirdan Thanks for the feedback 👍
You're right. This section of the README only targets the entry definition. Maybe it would be good if the plugin automatically would set the target property to node too.

[HyperBrain]

Opened a separate feature request for the improvement. Closing this issue now.

[swarajgiri]

Hey @HyperBrain - I am facing the same issue when trying to access process.env.BLA in functions.

'TypeError: Cannot read property \'BLA\' of undefined'

serverless.yml

frameworkVersion: "=1.24.1"
package:
  individually: true

provider:
  name: aws
  runtime: nodejs6.10
  stage: dev
  cfLogs: true
  region: us-east-1
  environment:
    BLA: test

custom:
  webpackIncludeModules: true 

plugins:
  - serverless-webpack
  - serverless-offline-scheduler
  - serverless-pseudo-parameters
  - serverless-offline

webpack.config.js

'use strict'

const nodeExternals                 = require('webpack-node-externals'),
      webpack                       = require('webpack'),
      path                          = require('path'),
      UglifyJSPlugin                = require('uglifyjs-webpack-plugin'),
      slsw                          = require('serverless-webpack'),
      LodashModuleReplacementPlugin = require('lodash-webpack-plugin');

module.exports = {
    entry: slsw.lib.entries,
    output: {
        libraryTarget: 'commonjs',
        path: path.join(__dirname, '.webpack'),
        filename: '[name].js'
    },
    target: 'node',
    externals: [
        nodeExternals(),
    ], 
    module: {
        rules: [
            {
                test: /\.js$/,
                loader: 'babel-loader',
                include: [
                    path.resolve(__dirname)
                ],
                exclude: [
                    path.resolve(__dirname, 'node_modules'),
                ],
                query: {
                    presets: [
                        [
                            'env',
                            {
                                'targets': {
                                    'node': '6.10',
                                    'uglify': false
                                },
                                'useBuiltIns': true,
                                'modules': false,
                                'debug': false
                            }
                        ]
                    ],
                    plugins: [
                        'transform-runtime',
                        'transform-async-to-generator',
                        'transform-export-extensions',
                        'transform-es2015-modules-commonjs',
                        'lodash',
                    ],
                }
            },
            {
                test: /\.json$/,
                loader: 'json-loader'
            }
        ]
    },
    plugins: [
        new LodashModuleReplacementPlugin({
            'collections': true,
            'shorthands': true
        }),
        new webpack.DefinePlugin({
            'process.env': {NODE_ENV: JSON.stringify('production')}
        }),
    ],
};

[HyperBrain]

@swarajgiri Your configuration looks good. Do you have the problem with more than one project or only with this one?

'TypeError: Cannot read property \'BLA\' of undefined' would even mean that process.env undefined.

You could do some checks:

• serverless package and check the generated CF template in .serverless for the function resource (check the environment)
• Disable all plugins but serverless-webpack and see if the environment variables are there
• try babel-preset-node6 instead of env to verify.

Strange is, that serverless-webpack does not do anything with the configuration of your functions - only serverless composes them. If the function configuration in the CF template or in the AWS console show the variable, then something with the configuration (webpack config) is wrong.

[swarajgiri]

@HyperBrain - I just encountered this issue in a new project. Wasn't using env variables before.
Also, checked aws lambda console. It shows the environment variables there.
Strange that i cannot access it in the functions.

Will try out the checks and report back.

[swarajgiri]

Tried out the suggestions, found that the cf template contains the env variables and they are also available on aws lambda console. Its just that the function does not find them.

function

module.exports.handler = (event, context, cb) => {
    const response = {
        statusCode: 200,
        body: JSON.stringify({
            'data':   process.env.BLA,
        })
    };
    cb(null, response);
};

serverless.yml

plugins:
  - serverless-webpack
  - serverless-offline

and
webpack.config.js

    presets: [
        'node6'
    ],

Same error in both cases
"errorMessage":"Uncaught error in your 'moveToPriorityQueue' handler","errorType":"TypeError","stackTrace":["TypeError: Cannot read property 'BLA' of undefined"

The env vars are present in cf template

    "MoveToPriorityQueueLambdaFunction": {
      "Type": "AWS::Lambda::Function",
      "Properties": {
        "FunctionName": "content-processing-dev-moveToPriorityQueue",
        "Handler": "moveToPriorityQueue.handler",
        "MemorySize": 128,
        "Role": {
          "Fn::GetAtt": [
            "IamRoleLambdaExecution",
            "Arn"
          ]
        },
        "Runtime": "nodejs6.10",
        "Timeout": 10,
        "Description": "Move processing requests to priority queues",
        "Environment": {
          "Variables": {
            "BLA": "test"
          }
        }
      },
    },

Node: v8.9.1
OS: Ubuntu 16.04.3 LTS

[swarajgiri]

@HyperBrain - Any ideas on what might be causing this?

[HyperBrain]

@swarajgiri Cannot read property 'BLA' of undefined actually means that it could not find process.env itself. The main reason for this is a missing target: "node" setting in the webpack config. Can you check that?