## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
Dustin Goodman
@dustinsgoodman
No worries! Thank you :)
David Hérault
@dherault
Does it crash the same way using v6.8.0?
Dustin Goodman
@dustinsgoodman
Pulling it down now to test.
All better in v6.8.0! :D
Closed the above issue with the notes regarding resolution. Thanks for the fix!
tan-t
@tan-t

hi!
I'm using serverless-offline 6.5.0 in my project, and want to test my functions which don't have an HTTP events with invocation endpoint (via aws-cli).
I remember when it was 5.10.0, the serverless-offline plugin just gave me invocation endpoint for all the functions like below:

...
Serverless: Routes for helloworld:
Serverless: POST /{apiVersion}/functions/myservice-dev-helloworld/invocations
...

but with 6.5.0, it seems that the plugin isn't giving invocation endpoints unless the function has an HTTP event.
I don't find any breaking changes or migration guides related to this in v6,
but when I downgraded my serverless-offline to 5.10.0, it started to create endpoints, so I think it is a version problem.

does anyone know how to make it create invocation endpoint for all the functions with serverless-offline v6?

tan-t
@tan-t
sorry I've mistakenly thought that the plugin is not making endpoints but it turns out that it is making them silently. with SLS_DEBUG=* , I can see invocation endpoints and they are working nicely actually.
David Hérault
@dherault
:thumbsup:
Ross Coundon
@rcoundon

I have a serverless.yml with a collection of lambdas. There are currently some API Gateway triggered lambdas and one that is SQS triggered.
The environment is set at the provider level.

I'm running this using serverless-offline and for SQS I'm using the serverless-offline-sqs-esmq plugin.

The peculiar thing is, for the API Gateway triggered lambdas, all the process.env values are set correctly. However, when the SQS triggered lambda runs, none of the environment variables set in serverless.yml are available. Serverless is setting something as I can see that the IS_OFFLINE property is set, just none of my own specified ones.

There is no difference in config other than the event source for the two different types. I've also tried specifying the environment at the function level but this makes no difference.

Has anyone seen this or know what it could be?

Thanks

Gurkiran Singh
@Gurkiran-Singh

Hi,
I am new to Serverless.
I just want to know if there is any way around that we can create s3 buckets using serverless if else plugin.

What I am trying to achieve is that I want to create new s3 buckets as per Stage I gave in if else statement.

Fr example if script(serverless.yml) runs in production stage it should create different s3 bucket and if script runs in development stage then it should create different bucket according to if else statement.

Please let me know if there is any way around to achieve this.

Vishesh M
@visheshCuriousDev
Hi guys !! Is there no hot reload for serverless offline ?
I run "SLS_DEBUG=* sls offline start". It run in debug mode but any changes made to any of the handler files, it does not reload !!! Any idea ?
Jack Fazackerley
@JackFazackerley

Hi I'm running serverless-offline v6.8.0, serverless v2.16.1, Go v1.15.5 and for some reason i can only GET, any time i POST it's as if serverless-offline is blocking me? The connection just hangs and there are no lo gs. The command i'm running is: SLS_DEBUG=* sls --verbose offline start --useDocker. My serverless file looks like:

service: example

frameworkVersion: '2'

plugins:
- serverless-offline

provider:
name: aws
runtime: go1.x
stage: ${self:custom.stage} region:${self:custom.region}

custom:
stage: ${opt:stage, 'develop'} region:${file(env.yml):regions.${self:custom.stage}} package: individually: true exclude: - ./** functions: api: runtime: go1.x handler: bin/api events: - http: cors: origin: '*' path: api method: any package: include: - bin/api environment:${file(env.yml):environment.example}.

I'm unsure if i'm doing anything wrong or it's the versions?

Ahmed Bayoumy
@bayoumymac
Hello, I have been running into this weird error on the second request after running sls offline start
node[91757]: ../src/env-inl.h:1036:void node::Environment::AddCleanupHook(void (*)(void *), void *): Assertion (insertion_info.second) == (true)' failed.
1: 0x10009ce91 node::Abort() [/usr/local/bin/node]
2: 0x10009cd1a node::AppendExceptionLine(node::Environment*, v8::Local<v8::Value>, v8::Local<v8::Message>, node::ErrorHandlingMode) [/usr/local/bin/node]
3: 0x10001f6be node::Environment::AddCleanupHook(void (*)(void*), void*) [/usr/local/bin/node]
4: 0x100008b00 node::AddEnvironmentCleanupHook(v8::Isolate*, void (*)(void*), void*) [/usr/local/bin/node]
5: 0x107903206 WrappedRE2::Init() [/Users/Test/Documents/instagram-bot/serverless/node_modules/re2/build/Release/re2.node]
6: 0x107903f23 node_register_module_v88 [/Users/Test/Documents/instagram-bot/serverless/node_modules/re2/build/Release/re2.node]
7: 0x10007bf86 std::__1::__function::__func<node::binding::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&)::$_0, std::__1::allocator<node::binding::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&)::$_0>, bool (node::binding::DLib*)>::operator()(node::binding::DLib*&&) [/usr/local/bin/node]
9: 0x10021da46 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/usr/local/bin/node]
10: 0x10021d0c9 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node]
11: 0x10021c8b0 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
12: 0x1007fd979 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit [/usr/local/bin/node]
Abort trap: 6
that only occurs on the second request, the first request goes through just fine
cdmpicker
@cdmpicker
anyone got serverless offline working with rollup?
Zhani Baramidze
@jbaramidze
hi!,
I've installed serverless offline plugin, all works good, port 3000 got exposed and handles fine, but for some reason it does not seem to expose 3002 to do Lambda invocations by hand. shouldn't it start working automatically?
Andy Swanson
@awswanson

Hello, I have been running into this weird error on the second request after running sls offline start

@bayoumymac Were you able to resolve this issue? The exact same thing is happening to me.

Jack Howard
@JackHowa
is there a good way of mocking alb? I'm seeing urls that aren't matching what I would expect running serverless-offline?
[offline] Lambda Invocation Routes (for AWS SDK or AWS CLI):
* POST http://localhost:3002/2015-03-31/functions/x-api-sandbox-getBundles/invocations
Jack Howard
@JackHowa
^ this is related to issue dherault/serverless-offline#598 if any one is working on this. I saw someone try to bounty it I think
Jack Howard
@JackHowa
also is there a way to specify a different serverless.yml file to run? I haven't been able to find the equivalent of --config equivalent to serverless. thanks for your help!
looks like it's being tracked here by dherault/serverless-offline#1146
Rafael Franco
@rfoel
How about releasing the support for nodejs14.x?
Zac Tolley
@ztolley
Another Vote here for 14. Is there ANY traction on this?
mikemeerschaert
@mikemeerschaert
Is there a way to just run one function with serverless offline when I have many functions defined in my serverless.yml file?
e.g. given my serverless.yml file looks like this, how do I just run functionB. I tried sls offline --functionB but that builds and starts all the functions, and function A takes a very long time to build. Also, I intend to build many more functions in the future, but I want to be able to run a single functional locally while working on it without having to worry about the rest.
service:
name: backend
plugins:
- serverless-webpack
- serverless-offline
provider:
name: aws
region: us-west-1
runtime: nodejs12.x
functions:
functionA:
handler: handler.functionAHandler
events:
- http:
path: functionA
method: post
- http:
path: functionA
method: get
functionB:
handler: handler.functionBHandler
events:
- http:
path: functionB
method: post
- http:
path: functionB
method: get
Jake Wood
@jakemwood
+1 for Node v14, as well as a +1 for dherault/serverless-offline#1175. I'm happy to help with either of these initiatives.
Zac Tolley
@ztolley
At what point do we have to resort to created an official fork?
selected-pixel-jameson
@selected-pixel-jameson
Does anyone know if this repo is still being supported? It seems as if @dherault has not responded since October. I'm just concerned as this is a pretty big part of a lot of peoples development and the repo now hasn't seen a new release for almost 6 months, was monthly prior to 6.8.0. I've created this question, dherault/serverless-offline#1193, on the github repo. First and foremost I hope that @dherault is ok, but would like to know if the community needs to have a discussion as to where this project is going.
Mirko Buholzer
@buholzer

I have an issue when running serverless-offline with the JWT Authorization function. serverless-offline tries to compare my jwt token with jwtOptions.issuerUrl that points to a cloudformation function.
My jwtOptions from createJWTAuthScheme.js look like this:

{
authorizerName: 'cognitoAuthorizer',
name: 'cognitoAuthorizer',
issuerUrl: { 'Fn::Join': [ '', [Array] ] },
audience: [ { 'Fn::ImportValue': 'authUserPoolClientId' } ]
}

Any way I can ignore issuerUrl and audience?

Arslan Ali
@arslanalidev
Hi Guys,

I am facing this below error while I am trying to run the serverless offline.
Error ---------------------------------------------------

Require stack:

C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless-offline\dist\checkEngine.js
C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless-offline\dist\index.js
C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless-offline\dist\main.js
C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js
C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\lib\Serverless.js
C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\scripts\serverless.js
C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\bin\serverless.js
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless-offline\dist\checkEngine.js:3:49)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless-offline\dist\index.js:13:1)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless-offline\dist\main.js:11:18)
at require (internal/modules/cjs/helpers.js:74:18)
at requireServicePlugin (C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:28:12)
at C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:164:20
at Array.map ()
at PluginManager.resolveServicePlugins (C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\lib\classes\PluginManager.js:161:8)
at Serverless.init (C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\lib\Serverless.js:171:30)
at async C:\Users\Arslan Titan\AppData\Roaming\npm\node_modules\serverless\scripts\serverless.js:235:7

Tim Stackhouse
@tstackhouse
How does one run the integration tests properly in order to contribute to the project?
I keep getting timeouts because it doesn't look like it's spinning up a local server
Dmitry Kireev
@AutomationD
Something common, prob ably, but Serverless command "offline start" not found. even after installing from "serverless-offline": "github:dherault/serverless-offline#master",