Serverless-webpack: watch with serverless offline

[isitgeorge]

This is a Question

Description

When using this plugin with Serverless offline, it transpiles as expected but is it possible to trigger a retranspile when a change is detected? Currently have to restart the serverless offline wrapper.

Thanks!

[SyedRFarhan]

I've been having trouble with this too. I use nodemon as a workaround. Here are the scripts:

"serve": "sls offline -P 4000",
"serve:watch": "nodemon -e js,ts,jsx,tsx -x yarn run serve",

[c-bandy]

This used to work for me, but after updating my package version it stopped working.

[isitgeorge]

This used to work for me, but after updating my package version it stopped working.

webpack used to watch and rebuild automatically?

[c-bandy]

Serverless offline with serverless-webpack did have the watch thing work, yeah

[soda0289]

Do you know which version broke watch?

[AshUK]

serverless-offline:
  useChildProcesses: true

[haroonKhan-10p]

facing the same issue. Using nodemon as a workaround works fine. But it is not as fast as serverless-webpack

[isitgeorge]

Published a little module that I was using internally to solve this, since asking the original question - https://www.npmjs.com/package/serverless-offline-multi but would be great to work out how/when the webpack watch broke

[polson]

Also wondering how to do this

[haroonKhan-10p]

webpack-watch is fixed by this: working on macOS Catalina.
Update serverless.yml to add custom attribute like this:

custom:
  serverless-offline:
    useChildProcesses: true

[c-bandy]

@AshUK @haroonKhan-10p Worth noting that these are not fixes, more so workarounds. They massively degrade performance, especially for larger projects.

[polson]

@haroonKhan-10p that unfortunately didn't do anything for me.

The issue for me is that webpack does watch and transpile correctly, but serverless offline uses cached files and not the new ones. I think the issue lies with the serverless-offline plugin

I think we will have to dig into the plugin and see if there's some way to fix it. I looked into it yesterday and I don't really see the problem, but I'll keep digging.

Also see this related issue: https://github.com/dherault/serverless-offline/issues/931

And this one: https://github.com/dherault/serverless-offline/issues/864

[francisu]

And this one: dherault/serverless-offline#864
The above is what broke it. This was a change introduced in serverless-offline 6.0.0