[Question] How to specify different formats for multiple exports?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, typescript
- Domain
- build-system, tooling
Research direction
The issue names no repository file or test, but includes package.json exports examples and the microbundle command. Start by reviewing the documented single-export and multiple-export examples; done means clarifying whether per-export format mappings are supported and documenting the applicable configuration or limitation.
Written by the indexing model from the issue text.
Description
I'm trying to setup microbundle to provide separate exports for several modules my package is exporting, like this:
{
"name": "x",
"type": "module",
"version": "10.0",
"author": "y",
"license": "MIT",
"devDependencies": {
"microbundle": "^0.15.0",
"np": "^7.6.1",
"typescript": "^4.6.4"
},
"dependencies": {},
"scripts": {
"prepare": "microbundle ./src/one.ts ./src/two.ts"
},
"exports": {
"one": "./dist/one.modern.js",
"two": "./dist/two.modern.js"
},
"files": [
"dist"
],
"types": "dist/index.d.ts"
}
However, I don't know how to specify different export formats for each one of my exports.
The documentations provides either this example, which shows how to proceed when doing "single" exports:
"exports": {
"require": "./dist/foo.cjs",
"default": "./dist/foo.modern.js"
},
or this example, which shows an example of multiple exports, but in a single format:
"exports": {
".": "./dist/foo.modern.mjs",
"./lite": "./dist/lite.modern.mjs",
"./full": "./dist/full.modern.mjs"
},
How could I specify multiple formats like in the 1st example, while still specifying multiple named exports like in the 2nd example?
- Dominant language
- JavaScript
- Stars
- 8.1k
- Forks
- 358
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from developit/microbundle
-
CSS
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
developit/microbundle#1002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
developit/microbundle#789 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
developit/microbundle#1100 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
developit/microbundle#1094 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
developit/microbundle#1093 · 3 comments · 1 reaction ·
All issues in developit/microbundle
Similar issues
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
georgestephanis/p2026#40 ·
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Margaret-Petersen/food-delivery-app-clone-react-native#1981 ·