Comments (6)
@juliusmarminge i get your point now
from t3-env.
afaik NUXT_FOO
isn't populated on client but you need to do NUXT_PUBLIC_FOO
, hence the pre-configured client prefix of NUXT_PUBLIC_
.
from t3-env.
@juliusmarminge What if I don't want to add PUBLIC_
? I just need NUXT_
. This option clientPrefix
should be exposed on userland.
from t3-env.
I dont think you understand what clientPrefix means. It's the thing you prefix your variabler with if you want the value sent to client. NUXT_ doesnt do that, NUXT_PUBLIC_ does.
from t3-env.
@juliusmarminge Currently, without using t3-env
my environment variables are prefixed with NUXT_
without adding PUBLIC_
, and it works fine, but adding this package will result in me changing my environment variables, which I really don't want to do.
from t3-env.
Currently, without using t3-env my environment variables are prefixed with NUXT_ without adding PUBLIC_, and it works fine
Then those should go in the server object
from t3-env.
Related Issues (20)
- Problems with package import in version 0.9.1, How can I make Jest work successfully? HOT 4
- Proposal to add extensions.json HOT 1
- Issue with Loading Environment Variables in Docker Container HOT 5
- Cannot find module '@t3-oss/env-core' or its corresponding type declarations. HOT 2
- Bundling Next.JS app results in environment key names exposed in the bundled js chunks HOT 2
- conditional environment variable based on environment HOT 4
- Vercel Server environment variables being populated HOT 2
- t2-env package dependencies vs devDependencies HOT 1
- SvelteKit + @sveltejs/adapter-node = "Attempted to access a server-side environment variable on the client"
- Error Missing "./dist" specifier in "@t3-oss/env-core" package HOT 6
- Request - ability to pass z.object{...}) as .server, .client, .runtimeEnv of createEnv method HOT 2
- Expose internal value for isServer
- Only usable in React Native with experimental features due to Package Exports?
- [repro]: SyntaxError: Cannot use import statement outside a module HOT 5
- Env validation on NextJS standalone output
- Multi-client prefixes
- Default values skipped when using SKIP_ENV_VALIDATION
- Service worker issue
- Support for conditionally requiring fields/envs?
- help needed for build checking
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from t3-env.