Marnix Heuker of Hoek
Marnix Heuker of Hoek
Yes that is what I thought too. It also automatically converts booleans to strings... Let me know if there is anything I can do to help
Hi @alegmal. I saw your comment on my question requesting help. I believe that your environment variable file must have the .env.js extension. So for example: myvars.env.js should work. The...
Now it seems the path is `/ignore/env.js` instead of `./ignore/env.js `. Can you confirm that it also doesn't work with `./ignore/env.js`? If that also doesn't work can you try to...
are you absolutely sure the path is correct? because the error seems to suggest that it simply can't find the file... Is the path relative to the same root as...
@psamim I believe you need the `.env.js` extension. just `.js` won't work. Also, I don't think absolute paths will work. I believe that npm can't look for files outside of...
@psamim Ah! That's interesting. What were the exact errors in the env file? This is probably something the maintainers would like to fix. @toddbluhm (I took the liberty of tagging...
@psamim Ah ok thanks for sharing that. My guess would be that all errors related to the env file incorrectly get caught and trigger the "file not found error".
Thanks @toddbluhm !!
For what it's worth: I just migrated a code base from `moment` to `day.js` and I too ran into this issue. The behavior of the two libraries differs here. `moment`...
Still running into the same issue. Related: #15191 #15222 So many people must be impacted by this...