Repository navigation
[Question] Sub-exports depending on main export bundle the entire main-export. #1027
Description
I have a project where I have a main-export and multiple other exports. The other exports are extensions that depend on the main-export, but I don't want them to be in the main-export to keep it as small as possible.
Users should be able to do:
import {Thing} from 'package';
// optional addition
import {OtherThing} from 'package/a';(or similarly using multiple script-tags with the umd-builds)
As for the source-files, it's roughly like this:
// index.ts
export * from './main';
// main.ts
export class Thing {}
// a.ts
import {Thing} from './main';
export class OtherThing extends Thing {}And the package.json contains these sub-exports:
"exports": {
".": {
"import": "./dist/index.modern.js",
"require": "./dist/index.js",
"umd": "./dist/index.umd.js",
"browser": "./dist/index.module.js"
},
"./a": {
"import": "./dist/a.modern.js",
"require": "./dist/a.js",
"umd": "./dist/a.umd.js",
"browser": "./dist/a.module.js"
},
}
With this, the output-files for './a' (all formats) have the entire definition of './main.ts' inlined.
So my question is, is there a way to configure microbundle to treat those other files as externals?
Activity
developit commentedon Feb 18, 2023
You need to import the package name in your source, not the entry filename:
usefulthink commentedon Feb 20, 2023
Thanks a lot for the quick response!
I tried that, and first got the following error:
So I tried to tell typescript about the package:
That compiles without error, but unfortunately didn't change anything in the output (still contains everything from the main.ts in a.ts' output).
The next thing I tried was to instead specify the path as
.:but that leads to the following error:
I finally solved it, by explicitly telling microbundle to treat the module as external (and using the first solution from above to make typescript happy):
Is that something that microbundle should have been able to pick up on automatically?
bhollis commentedon Aug 15, 2023
I ran into a similar issue - @usefulthink your solution worked, but it means the UMD build now contains a
requirecall rather than being all bundled together. I think this is probably something where microbundle needs to be smart about settingexternaldifferently for different outputs.