Releases: friggframework/frigg
Releases · friggframework/frigg
v2.0.0-next.20
🐛 Bug Fix
@friggframework/core
- Turns out it wasn't the credentials, it was allowedHeaders. Making this generic/all. #387 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.19
🐛 Bug Fix
@friggframework/core
- Removing credential: true from cors options as it contradicts the origin: '*' option #386 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.18
🐛 Bug Fix
@friggframework/core
- Missing dotenv from a prior release #385 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.17
🐛 Bug Fix
@friggframework/core
- Just adding lodash.get for now, some obvious cleanup for later. #384 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.16
🐛 Bug Fix
@friggframework/core
- Simple fix for now, may have unintented side effects depending on where Frigg Start is run from. But let's go with simple. #383 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.15
🐛 Bug Fix
@friggframework/core
,@friggframework/devtools
- Updated so that devtools depends on core, and no dependency on devtools from core. #382 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.14
🐛 Bug Fix
@friggframework/core
,@friggframework/devtools
- Updated so that devtools depends on core, and no dependency on devtools from core. #381 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.13
🐛 Bug Fix
@friggframework/core
- Added cors package. Let's see what else pops when we deploy. #380 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.12
🐛 Bug Fix
@friggframework/core
,@friggframework/devtools
- Replaced serverless-webpack with serverless-jetpack for now, it did a good job finding parent dependencies. Might go back to webpack at some point. This should resolve ommitted node_modules. Not perfect #379 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)
v2.0.0-next.9
🐛 Bug Fix
@friggframework/devtools
- Default visibility timeout is 30 seconds but the queue worker lambda timeout limit is set to 10 minuets, and that's a nono according to the powers that be (for good reason). #376 (@seanspeaks)
Authors: 1
- Sean Matthews (@seanspeaks)