awslabs / awslabs/aws-crt-nodejs

Add Esbuild support

Open
#467 15 comments 17 reactions 0 assignees View on GitHub
CRT/IoT feature-request p2
Dominant language
TypeScript
Stars
43
Forks
32
Avg merge
1d 17h
Merged PRs (30d)
1

Description

### Describe the feature

Using esbuild to build/package a JS project that uses the CRT is an exercise in frustration. We should smooth the sharp corners and provide README and/or sample-based guidance for people who wish to use esbuild.

Ideally we should provide solutions that
1. use the browser distribution
2. use the node distribution and support flexible lookups for the NAPI module, with detailed instructions

We may want to special case Lambda as well with a targeted sample.

We've also had a request for flexible NAPI module path lookup here: https://github.com/awslabs/aws-crt-nodejs/issues/214

I believe proper esbuild support would have to include flexible NAPI module resolution, and so I'm consolidating that request into this feature request as well.

### Use Case

N/A

### Proposed Solution

_No response_

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are identified in the issue. Begin by examining the esbuild packaging paths and the browser and node distributions; done means documented or sampled guidance for both distributions, flexible NAPI module lookup, and any needed Lambda-specific support.

Written by the indexing model from the issue text.

Assessment

Tech stack
nodejs, typescript
Domain
build-system, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.