- Upgraded dependencies
- #105 - Warning probably not needed for semver minor changes
- #108 - Call command does not appear in help text
- Upgraded dependencies
- #103 - Prevent emulator from hanging from requiring user code that doesn't exit., by @laurenlong
- Upgraded dependencies
- Hid some annoying warning messages
- Add ability to set more options on the Emulator child process
- #92 - Switch to
host
andbindHost
options, by @kpruden- Fixes #91 (Support connecting to an emulator behind a NAT)
- #89 - Refactor how the logs work, by @laurenlong
- Added a
--tail
option tofunctions start
. Iftrue
,functions start
will not exit right away. Instead the Emulator's logs will be streamed to the terminal. Pressing Ctrl+C would stop the Emulator.
- Added a
- Upgraded dependencies
- #73 - Warn user when local version of Node is greater than 6.9.
- When calling
Controller#start
programmatically, you can now pass an options object to configure the child process, and you'll receive the handle to the child process when the promise resolves. - Add a
getOperation
method to the clients - Added more debug logging
- #84 - Support for testing a database trigger
- Function timeouts now work
- Fixed gRPC client request deadlines
- Hopefully fixed the following (they're hard to reproduce):
- #71 - "status" option produces bad 'HTTP Trigger' path
- Fixes undefined method error when trying to invoke functions that don't exist.
- #69 - Move --debug and --inspect into their own commands. Debugging has changed, please see Debugging-functions for details.
- #64 - Can start Emulator with mismatching versions
- Some options have been removed from commands where they weren't needed
- Cleaned up of the CLI help text
- Export all Emulator classes
- #62 - Add support for live-reloading of functions. Function workings will now automatically shutdown when they detect changes to the function's code. A new worker will be started the next time the function is called.
- #48 - Deploying an already deployed function should update the existing function, not fail
- #35, #44 - Re-architect to process per function, allowing simulation of "warm" functions
- #43 - Improve upgrade awareness of the Emulator. CLI and Emulator version can no longer mismatch.
- #31, #54 - Cleanup temporary archives
- #52 - Display on default console window in Mac is difficult to read
- #46 (again) - Inconsistent behaviour for parsing path and path params
- #53 - HTTP Function hangs when debugging
- #56 - Deployments are slow
- #60 -
GCP_PROJECT
environment variable not set
- #47 - Sometimes function is killed before it reports result
- #46 - Request path not forwarded to function
- #45 - Cannot Pass query string to cloud functions
- #38 - Cannot find module 'upgrade-warning'
- This release includes a complete rewrite of the entire Emulator.
- Documentation for the new release can be found at https://github.com/GoogleCloudPlatform/cloud-functions-emulator/wiki
- If you have trouble upgrading, delete the following folder:
- OSX/Linux -
/Users/YOUR_USERNAME/.config/configstore/@google-cloud/functions-emulator
- Windows -
C:\Users\YOUR_USERNAME\.config\configstore\@google-cloud\functions-emulator
- OSX/Linux -
- The emulator now requires Node.js v6.9.1 so as to match the production Google Cloud Functions environment.
functions call
- Switched position ofmodulePath
andfunctionName
arguments for consistency with other commands.- Moved the config file from
config.js
to aconfig.json
file in the user's home directory.
- Added
functions config list
andfunctions config set
commands.
- Refactored the tests to exercise the CLI itself.
- Lots of architectural changes in the code for better maintainability, testability, and extensibility.
- Adds checks to deploy command to ensure module path is a directory
- Adds more clarity to README for deploy command
- Initial Release