Suggestion for Documentation Improvement on Namespace Imports and Tree Shaking

I think the docs on Namespace imports should idealy provide a link to explain why "Named imports may generate tree shaking issues when a bundler doesn’t support deep scope analysis.". Because I don't know why and it's totally counter-intuitive (

import * as Effect from "effect/Effect"

import * as Effect from "effect/Effect"

is easier to tree-shake than

import { Effect } from "effect"

import { Effect } from "effect"

? Wuut?)

Communities Docs About Terms Privacy

Suggestion for Documentation Improvement on Namespace Imports and Tree Shaking - Effect Community

Suggestion for Documentation Improvement on Namespace Imports and Tree Shaking

Similar Threads

Suggestion for Documentation Improvement on Namespace Imports and Tree Shaking

Similar Threads

Similar Threads

Similar Threads