Why is the .env file loaded when running locally?

Open
#437 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, javascript, node.js
Domain
cli, cloud

Research direction

Start by reading the deployment explanation in issue #301 and trace how node-lambda run handles the .env file. Determine whether loading it locally is intentional; done should be a documented rationale or a clearly specified behavior change.

Written by the indexing model from the issue text.

Description

question

If the .env file is used for deployment as explained in #301 then it seems counter intuitive to load it when using node-lambda run. Is there any reason behind this or am I missing something?

Dominant language
JavaScript
Stars
1.4k
Forks
185
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from motdotla/node-lambda

All issues in motdotla/node-lambda

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.