NONINFRINGEMENT.This Serverless plugin emulates AWS λ and API Gateway on your local machine to speed up your development cycles. OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,ĮXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES Included in all copies or substantial portions of the Software. The above copyright notice and this permission notice shall be Software is furnished to do so, subject to the following Restriction, including without limitation the rights to use,Ĭopy, modify, merge, publish, distribute, sublicense, and/or sellĬopies of the Software, and to permit persons to whom the Obtaining a copy of this software and associated documentationįiles (the 'Software'), to deal in the Software without

Permission is hereby granted, free of charge, to any person Support: if you find any problems with this module, email / tweet / License: MIT - do anything with the code, but don't blame me if it does not work. Start-server-and-test parsed args: ' test ' Start-server-and-test parsing CLI arguments: +0ms To see diagnostic messages, run with environment variable DEBUG=start-server-and-test $ DEBUG=start-server-and-test npm run test Thus you need to use http-get:// URL format to force wait-on to use GET probe or ask for a particular resource. Wait-on uses HEAD by default, but webpack-dev-server does not respond to HEAD only to GET requests. Under the hood this module uses wait-on to ping the server. You can watch the explanation in the video Debug a Problem in start-server-and-test. Start-server-and-test # or maybe the server responds to HEAD requests to JS resource # maybe the server responds to HEAD requests to the HTML page You can force the start-server-and-test to ping the server using GET requests using the http-get:// prefix: start-server-and-test http-get://localhost:8080Īs an alternative to using GET method to request the root page, you can try pinging a specific resource, see the discussion in the issue #4. You have two solutions: Use HTTP GET requests $ curl -head If the server responds with 404, then it does not handle the HEAD requests. # from the second terminal call the server with HEAD request You can check if the server responds to the HEAD requests by starting the server and pinging it from another terminal using curl # from the first terminal start the server If you are using webpack-dev-server (directly or via angular/cli or other boilerplates) then the server does not respond to HEAD requests from start-server-and-test.

'ci ': 'start-server-and-test 'yarn start-server' 'yarn test' '

Npm install serverless offline