Describe the bug
Both dynamic/private and dynamic/public export the variables as env
import { env } from '$env/dynamic/private'; // ok
import { env } from '$env/dynamic/public'; // "env" is already defined !!
It is a bit surprising (to not say disappointing) that this wouldn't work out of the box for an otherwise excellent framework.
Reproduction
NA
Logs
System Info
Severity
annoyance
Additional Information
Can be easily worked around with:
import { env as pubenv } from '$env/dynamic/public';
(perhaps it is enough to add this example to docs in one of those red boxes ?)
Describe the bug
Both
dynamic/privateanddynamic/publicexport the variables asenvIt is a bit surprising (to not say disappointing) that this wouldn't work out of the box for an otherwise excellent framework.
Reproduction
NA
Logs
System Info
Severity
annoyance
Additional Information
Can be easily worked around with:
(perhaps it is enough to add this example to docs in one of those red boxes ?)