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
{{ message }}
This repository has been archived by the owner on Jul 8, 2020. It is now read-only.
Is there any way I can access my variables from the .env file in order to
utilize them in my package.json scripts?
I'm attempting to store an API_KEY in the .env file and then pull it into
a script in order to publish some bundles + source maps to Bugsnag.
If possible, I'd love to not have to hard code this API key in the script
itself.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#49>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAzRJSuTc65TYioiXvjXQVpOrWUVJYifks5uRf2CgaJpZM4WAuSD>
.
Is there any way I can access my variables from the
.env
file in order to utilize them in mypackage.json
scripts?I'm attempting to store an API_KEY in the
.env
file and then pull it into a script in order to publish some bundles + source maps to Bugsnag.If possible, I'd love to not have to hard code this API key in the script itself.
I've attempted the following script in my
package.json
file:and, when run, have received the following output:
Any ideas how I can access variables in my
.env
file?The text was updated successfully, but these errors were encountered: