serverless-offline-sqs incompatible with new versions of serverless-offline about serverless-plugins

[bakasmarius]

serverless-offline is now version 6.1.0 - any plans on supporting v6?
I'm stuck with v6.0.0-alpha.8, any newer version throws this error:
Error: Cannot find module 'serverless-offline/src/functionHelper'

This commit might be worth looking into: dherault/serverless-offline@85e0c2c

[esetnik]

@christophersbarrett I have a workaround that's working and I pushed #125. Please check it out and let me know if it's working for you.

To test it in your project the easiest way is to grab the source code and place it into your local plugins folder e.g.:

 - ./plugins/serverless-offline-sqs.js

[oguimbal]

+1

I tried to investigate... but it turns out that this is not an easy fix without any prior knowledge. serverless-offline has changed quite a bit since 6.0.0-alpha.8.

Some details: Several plugins of this repo (I use serverless-offline-sqs and serverless-offline-dynamodb-streams) are using nasty internal functions of serverless-offline to trigger lambda processing, but these functions do not exist anymore. The core model of serverles-offline has changed dramatically. The commit referenced by @bakasmarius was just moving the incriminated functions, but they have now disapeared completely.

Wokaround (kind of): Use [email protected] :/
nb: This version required (for me) a nasty fix in node_modules\serverless-offline-dynamodb-streams\src\index.js - I had to invert functionName and __function arguments, at line 95 & 96.

[thetumper]

npm warns of the version requirement during install:

npm WARN [email protected] requires a peer of serverless-offline@^5.12.1 but none is installed. You must install peer dependencies yourself.

[Deliverart]

Any news on the @bakasmarius issue?
I have the same problem!

[christophersbarrett]

Has anyone brought this package up to date locally that they could potentially create a PR for? :-D :-D

[bakasmarius]

@esetnik thanks!! I'll try to find some time this week to check your PR locally, no promises though 😬

[bakasmarius]

@esetnik I couldn't get it to work, left a comment in your PR

[AdrieanKhisbe]

Handled by #129, hence closing