fix: issue with explicit side effect modules not tracking downstream - #286
Conversation
🦋 Changeset detectedLatest commit: 7beac39 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (5)
📒 Files selected for processing (6)
WalkthroughThe client build now propagates side-effect import markings from tracked importers to eligible resolved modules. Marko files, styles, and Vite assets remain excluded from propagation. The browser-side-effects fixture adds a nested side-effect module and a ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #286 +/- ##
==========================================
- Coverage 77.53% 75.41% -2.13%
==========================================
Files 14 16 +2
Lines 819 1212 +393
Branches 221 340 +119
==========================================
+ Hits 635 914 +279
- Misses 142 236 +94
- Partials 42 62 +20 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Carry a template's explicit bare
import "x"side effect marking downstream to the modulesxitself imports. Previously onlyxwas exempt from the client build's side effect free default, so a package whose effect lives in a module it bare-imports (eg terser installingAST_Toplevel#resolve_definesfromimport "./global-defs.js") still had that module shaken out. Marko files, styles and assets remain non-propagating, so a template's own imports stay shakeable.