Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Suggestion] Allow specifying external module names for UMD (rollup output.globals)
See original GitHub issueCurrent Behavior
Expected behavior
It does guess the names correct in this case but a nicer output would be great. You may notice that guessed name for the last react-dom is not even visible. It could lead to unexpected results if it would guess in the wrong way.
Suggested solution(s)
I wonder why it’s not possible to specify externals in a similar fashion as microbundle does. Since it would be optional, it doesn’t make the whole experience of zero configuration any worse.
Additional context
Used in building the https://github.com/JustFly1984/react-google-maps-api
Your environment
| Software | Version(s) |
|---|---|
| TSDX | 0.6.1 |
| TypeScript | 3.5.1 |
| Browser | N/A |
| Yarn | 1.16.0 |
| Operating System | Windows x64 |
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Well, as I said, why not to get inspired by microbundle? I like the way they tackled it in there with CLI option.
https://github.com/developit/microbundle#all-cli-options
So
tsdx.config.jswas added in #183 and released in v0.9.I think configuring Rollup’s
output.globalsandexternalsis much easier via that than via CLI, so I’m going to close this out