Esbuild watch with sls offline not working
See original GitHub issueHello. I’ve added a watch pattern in esbuild config
watch:
pattern: [ 'src/**/*.ts']
it’s recompiling code after changes, but those changes are not working
like if i add console.log('hello')
it will recompile but i won’t see that console.log() anywhere
same for other changes
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Esbuild - Serverless Framework: Plugins
serverless-esbuild. Serverless plugin for zero-config JavaScript and TypeScript code bundling using promising fast & furious esbuild bundler and minifier.
Read more >serverless-esbuild - Victor Korzunin - GitHub Pages
A Serverless framework plugin to bundle JavaScript and TypeScript with extremely fast esbuild.
Read more >serverless-esbuild - npm
Serverless plugin for zero-config JavaScript and TypeScript code bundling using extremely fast esbuild. Latest version: 1.34.0, ...
Read more >A Serverless Framework Plugin to Bundle JavaScript ... - Morioh
serverless-esbuild. Serverless plugin for zero-config JavaScript and TypeScript code bundling using promising fast & furious esbuild bundler and minifier ...
Read more >serverless AWS deployment fails because of esbuild
If you are installing with npm, you can try ensuring that both npm and node are not running under Rosetta 2 and then...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
try
--reloadHandler
with serverless offlineAre you certain it’s not this long standing issue with serverless-offline (https://github.com/dherault/serverless-offline/issues/864) ?
Enabling
--useChildProcesses
fixes this.