You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's no simple way to include code in client/server bundle only when a specific plugin/framework option has a specific value at build time.
Example
In any Vite-compiled module:
// @toggle foocallSomeFunction(...args)
The foo toggle should be registered with Saus at build time:
exportfunctionMySausPlugin(options){return{name: 'my-saus-plugin',saus({ toggles }){// The `foo` option of my plugin decides if "foo" toggle is removed.if(options.foo){toggles.use("foo")}}}}
In the above example, if the foo option of MySausPlugin is falsy, the callSomeFunction line is removed at build time.
Ideally, plugins would use namespaces in their toggle IDs:
The Problem
There's no simple way to include code in client/server bundle only when a specific plugin/framework option has a specific value at build time.
Example
In any Vite-compiled module:
The
foo
toggle should be registered with Saus at build time:In the above example, if the
foo
option ofMySausPlugin
is falsy, thecallSomeFunction
line is removed at build time.Ideally, plugins would use namespaces in their toggle IDs:
The text was updated successfully, but these errors were encountered: