Hello bubblers,
Pushed a couple of updates to the ‘Env’ Environment variable plugin:
The demo & documentation have also been updated.
Its’ backward compatible. So if you’ve previously purchased the plugin, simply update the version in your plugins tab.
Cheers,
Gaurav
Hassle-free setup without any need for database, workflows or custom states
Run a JavaScript code, and map a variable in your code to an Env variable
Screen recordings showing how the demos were built:
Setup video 1 - Sharing & syncing data across reusables and triggering workflows:
Setup video 2 - Run a JavaScript code, and mapping the output to an Env variable:
Awesome @gaurav!
One of my most-used plugins.
By the way, one challenge with the plugin (which is not a bug, but a general Bubble issue as far as I know), is that if the Env. Variable element is hidden when the variable is set, it will not receive the data until you “rewrite” the variable content again. This is especially a challenge with reusables, that are often invisible by default until they’re needed. It can easily be solved with workflows of course, but I’m curious if there are other ways this could be solved.
Something like a checkbox “Automatically fetch value when element becomes visible” or something. Is that something that could be implemented? Or do you know of an easy fix that I’m overlooking?
This version fixes that 
The only thing is that an Env needs to visible once for the code to load (that’s a bubble restriction).
Also you don’t actually need an Env element to set the variable. There’s a workflow step ‘Set Env’ which allows you to do this without any element.
Perfect 
Also you don’t actually need an Env element to set the variable. There’s a workflow step ‘Set Env’ which allows you to do this without any element.
Ah, I thought the workflow needed the Element to work. Thanks for the tip
Element actions need element to be visible. Workflows don’t. The Env variables supports both formats
Tested working, thanks!
@gaurav would be possible for you to add the ability to conditionally check ‘update value’
Done. Just pushed an update changing the checkbox to dynamic yes / no
I’ll be buying this tonight, been meaning to for a while
Thanks!!!
You, my friend, are a BUBBLE HERO! This is awesome! Pair this with an If-Then-WF and you can do just about anything 
I’ll be updating my plugin today!
I did not know this. For clarification, if I use an Env called activejob in one reusable, I can set the value of that Env from a second reusable without adding an Env on the second reusable?
Haha thanks @eli 
Oh yes absolutely… reusable, repeating group, main page etc. anywhere you can run a workflow from, you can set the value of an env. The element is required only to create & read the value of an env
Rockstar!
Page by page my app is changing from this:
To this:
The ability to store 6 variables in one Env is so much cleaner and more manageable.
There’s a nifty little preview feature as well there If you want to quickly see the variable names you’ve defined in the element just increase the size and it’ll list those as preview
You my good man are just on a charm offensive today 
Hi @gaurav, is it possible to read a variable from a different page in the app?
I just want to add some instructions here as I spent about a half hour testing to figure this out…specifically one detail that is essential to functionality
why do you use underscores all the time just write camelCase
