ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A low-traffic site wants its JavaScript payload kept as small as possible so per-visit transfer and deployment overhead stay low. Rollup's tree-shaking is the main lever for cutting unused code from the bundle, and the plan is to rely on its static analysis of ES modules rather than manually pruning imports across the dependency graph. The unresolved point i
Goal Enable tree-shaking of namespace imports ( import * as ns from 'pkg' ) when a dependency declares "sideEffects": false in its package.json , so that unused bindings are eliminated from the bundle. Constraints and uncertainty Rollup 4.x currently treats namespace imports as opaque references that prevent elimination of any exported binding, even when the
Component Import Strategy for Bundle Optimization In a low-traffic Angular application, reducing the initial JavaScript payload is a primary goal to minimize client-side load costs. PrimeNG supports granular, per-component imports to facilitate tree-shaking and reduce the final bundle size. While importing only the necessary components (such as AutoCompleteM
Rollup builds a static module graph from ES module import and export declarations and uses that graph for tree-shaking and code splitting. The goal is to clarify the documented decision rules for which exports are considered unused and removed, and which modules are emitted into separate chunks for lazy loading. Constraints include purely static analysis wit
Diagnosing duplicate root-provided service instances A service decorated with providedIn: 'root' should resolve to a single instance within the root EnvironmentInjector tree. In a standalone Angular 17+ application using loadComponent() for lazy routes, the same service class appears in multiple lazy chunks after production build, causing separate constructo
Context For a low‑traffic web app, every kilobyte of JavaScript counts. Core‑JS 3 offers selective imports (e.g., import 'core-js/modules/es.array.flat'; ) and a runtime detector ( import 'core-js/actual'; ) that can trim polyfills. Babel’s useBuiltIns: "usage" automatically injects only the polyfills that the target browsers actually need. However, Core‑JS
A small-scale application currently utilizes the full lodash package. To reduce the production bundle size, there is a need to transition to a more modular import strategy. The primary goal is to minimize the JavaScript payload without introducing runtime regressions or duplicate utility instances. Two documented approaches exist: importing specific methods
Goal The objective is to reduce the production bundle size for a low‑traffic Angular application that only uses a handful of PrimeNG components (e.g., ButtonModule , MenuModule ). By importing components via ES module entry points (v13+), Angular’s build optimizer can tree‑shake unused PrimeNG code. However, the peer dependency primeicons remains in the bund
Transitioning to Modular Router Definitions The shift from tRPC v9 to v10 introduced a redesigned API architecture that decouples the router definition from the server instance. This change is intended to improve tree-shaking and allow for a more granular TypeScript-first approach to API definitions. When implementing complex nested routers, there is a desig
rollup
angular
corejs
lodash
javascript
typescript