ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Context We are upgrading a component library (consumed by several internal apps) from core-js 2 to core-js 3. The major version change reorganized the import paths — our existing core-js/fn/array/from style specifiers no longer resolve, and the documented replacements are prefixed entry points such as /es/ , /stable/ , /features/ , and /stage/ . The unresolv
Integration boundary A workspace contains an application plus several shared packages. The app and one package load the global core-js build (core-js 3), while another package imports from core-js-pure to avoid polluting globals. The goal is to decide which mode the shared library should declare as a dependency, given that both builds ship the same implement
A shared JavaScript library consumed by several applications needs to polyfill newer ECMAScript features, and the team must pick one core-js import strategy before publishing. The documented options behave differently: global entry points such as core-js/stable or per-feature paths like core-js/actual/array/group-by patch built-in prototypes and globals, whi
corejs