Bug: `sam build` Ignores Files in dist/ Directory When Specified in .gitignore about aws-sam-cli

[lucashuy]

Hi, normally sam build is capable of building your Typescript project using esbuild as a build method (docs). Using tsc to perform a "preprocessing" build, then using sam build will have unintended side effects depending on the project structure.

Namely, that sam build will have it's own build process that may or may not include the dist folder. sam build will call npm pack under the hood to create a "production" ready copy of the project. npm pack will ignore any files that is listed in either .gitignore, or .npmignore, preferring to use .npmignore if both files exist. This may be the root cause of the issue you are facing.

Can you provide a sample project that utilizes your build process to help us further diagnose?

[hcz1]

Thank you for getting back to me. I’m currently on holiday and will get back to this the week of 9th September.

…

On Wed, 28 Aug 2024 at 20:07, Lucas ***@***.***> wrote: Hi, normally sam build is capable of building your Typescript project using esbuild as a build methods (docs <https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-build-typescript.html>). Using tsc to perform a "preprocessing" build, then using sam build will have unintended side effects depending on the project structure. Namely, that sam build will have it's own build process that may or may not include the dist folder. sam build will call npm pack under the hood to create a "production" ready copy of the project. npm pack will ignore any files that is listed in either .gitignore, or .npmignore, preferring to use .npmignore if both files exist. This may be the root cause of the issue you are facing. Can you provide a sample project that utilizes your build process to help us further diagnose? — Reply to this email directly, view it on GitHub <#7402 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADSIDVMPBHPQZH7EHK3K4YLZTYNW3AVCNFSM6AAAAABNBSVQ4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJWGA3DMMZWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>