Support AMD as input format
- Dominant language
- Go
- Stars
- 40.1k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
Would it be possible to process AMD-formatted JavaScript modules?
Context: I’m trying to ‘build’ several older versions of jQuery into bundles without depending on npm tooling, and they only moved to more modern module systems in more recent commit on their (unreleased) `main` branch
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing esbuild's existing CommonJS and ESM module handling, then compare the requested AMD input behavior with the jQuery versions described in the issue. Done would mean AMD-formatted JavaScript modules can be processed into bundles without npm tooling; no files or tests are named, so the implementation entry point and validation coverage must first be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100