Danilo Campana Fuchs

@dimitrius1986 Unfortunately, the code in which I implemented this functionality is private. I can, however, paste this snippet of how it was implemented: ```javascript import { IAnnotation, IGeometry } from...

I recommend using `FutureOr` instead of `Future` so it is more flexible and does not break existing implementations

When I implemented this, I used the create-react-app code as a sample. I now see this reduce may be causing issues. https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/config/env.js

> Is that why `.env.local` takes precedence over `.env`? `.local` should always have higher priority then their non-local equivalents. This is by design to allow a single dev to override...

@feeh27 `.env.local` is intended to override `.env`. This is by design, not a bug. You should not commit `.env.local` to your git repo. If you are running the deployment on...

I think we could add a new option `stage` and let users choose between `${env:NODE_ENV}` or `${self:provider.stage}`

> It looks like this repo is not maintained anymore, sadly. @danilofuchs have you perhaps built and published a version of your fork? Yes, I assume the repo owner migrated...

@falkenhawk I didn't even remember this, but I pushed a `with-builds` branch when testing this. Check if you can use it

You cannot ask again, but you can link them to your app's page on the settings app

@vanlooverenkoen I'm no longer working on the project, sorry I cannot reproduce it anymore.