@macklinu I figured it out.

Output:

> ncc build src/services/foo/handler.ts -o dist

0kB  dist/common/interfaces/Foo.ts
0kB  dist/common/config.ts
0kB  dist/common/log.ts
3kB  dist/index.js
3kB  [1934ms]

src/index.ts

import { APIGatewayProxyEvent, APIGatewayProxyResult } from "aws-lambda";
import { FOO } from "./common/config";

export const foo = async (
  _event: APIGatewayProxyEvent
): Promise<APIGatewayProxyResult> => {
  return {
    statusCode: 200,
    body: FOO
  };
};

src/common/config.ts

import { join } from "path";
import { config } from "dotenv";

const root = (file: string): string => {
  return join(__dirname, "..", "..", file);
};

config(root(".env"));

export const FOO = process.env.FOO;

You can put anything in src/common that isn't require(*)'d anywhere and it will get included in the distribution (notice interfaces/Foo.ts and log.ts are included but not required)

{
  "compilerOptions": {
    "target": "es2015",
    "moduleResolution": "node"
  }
}

So where this is happening is the line:

join(__dirname, "..", "..", file);

I simplified this example (mine uses dynamic .env files). If I remove the dynamic aspect and hardcode the join to:

config(join(__dirname, "..", "..", ".env"));

then, common/* is not being included.

Interesting...

.ts files being added to the end build #156

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions