Add field to package.json to output an unminified build - #1097
Draft
andrewiggins wants to merge 4 commits into
Draft
andrewiggins wants to merge 4 commits into
andrewiggins wants to merge 4 commits into
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
Copy link
Copy Markdown
⚠️ No Changeset foundLatest commit: bf19e48 Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset. This PR includes no changesetsWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Click here to learn what changesets are, and how to add one. Click here if you're a maintainer who wants to add a changeset to this PR |
Sorry, something went wrong.
andrewiggins
marked this pull request as draft
October 23, 2025 21:58
andrewiggins
force-pushed
the
debug-field
branch
from
76d0086 to
54e48b4
Compare
October 24, 2025 00:39
andrewiggins
force-pushed
the
format-repo
branch
from
0a134ab to
74fdad6
Compare
October 24, 2025 01:04
andrewiggins
force-pushed
the
debug-field
branch
from
54e48b4 to
1e51a12
Compare
October 24, 2025 01:05
Copy link
Copy Markdown
Collaborator
Not sure on your specific intent here, but a while back I toyed with doing just this with Preact and found it absurdly easy to break apps by pulling in two copies at once. Ensuring the entire module graph resolves just to the debug build is just as tricky as trying to avoid the dual package hazard and users aren't going to understand the intricacies. I'm not against adding this, it may be useful for Microbundle users, but I don't think we can ship it with Preact stuff in particular. Way too easy for folks to break their apps and get the (incredibly opaque) __H errors. |
Sorry, something went wrong.
andrewiggins
force-pushed
the
debug-field
branch
from
1e51a12 to
8b91262
Compare
October 24, 2025 01:29
Copy link
Copy Markdown
Contributor
|
Size Change: 0 B Total Size: 65.9 kB ℹ️ View Unchanged
|
Sorry, something went wrong.
andrewiggins
force-pushed
the
debug-field
branch
from
8b91262 to
bf19e48
Compare
October 24, 2025 01:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm often wanting to step through the source of Preact or Signals, but doing this is difficult since we ship minified code. In this PR I add an option to microbundle to output a "debug" build. This debug build is just an unminified ESM bundle of the library.
Consumers of microbundle libraries can then setup an alias in their bundle to use this build output when they want to step through sources of libraries of microbundle libraries.
NOTE: This format DOES NOT support React-style development vs production builds. This format only produces an unminifed build of the same source that is minified in other builds. However it should only be used for development. We have tuned the minification options to produce better than average minification and so those minified builds should be used in production bundles.