@@ -162,13 +162,23 @@ Creates a new `Server` object where:
162
162
[ ` server.state() ` ] ( #serverstatename-options ) or implicitly (without definition) using
163
163
the [ state configuration] ( #serverstatename-options ) object.
164
164
165
- - ` debug ` - determines which logged events are sent to the console:
165
+ - ` debug ` - determines which logged events are sent to the console (this should only be used
166
+ for development and does not affect which events are actually logged internally and
167
+ recorded). Set to ` false ` to disable all console logging, or to an object with:
168
+ - ` log ` - a string array of server log tags to be displayed via ` console.error() ` when
169
+ the events are logged via [ ` server.log() ` ] ( #serverlogtags-data-timestamp ) as well as
170
+ internally generated [ server logs] ( #server-logs ) . For example, to display all errors,
171
+ set the option to ` ['error'] ` . To turn off all console debug messages set it to ` false ` .
172
+ Defaults to uncaught errors thrown in external code (these errors are handled
173
+ automatically and result in an Internal Server Error response) or runtime errors due to
174
+ developer error.
166
175
- ` request ` - a string array of request log tags to be displayed via ` console.error() ` when
167
- the events are logged via [ ` request.log() ` ] ( #requestlogtags-data-timestamp ) . Defaults to
168
- uncaught errors thrown in external code (these errors are handled automatically and
169
- result in an Internal Server Error response) or runtime errors due to developer error.
170
- For example, to display all errors, change the option to ` ['error'] ` . To turn off all
171
- console debug messages set it to ` false ` .
176
+ the events are logged via [ ` request.log() ` ] ( #requestlogtags-data-timestamp ) as well as
177
+ internally generated [ request logs] ( #request-logs ) . For example, to display all errors,
178
+ set the option to ` ['error'] ` . To turn off all console debug messages set it to ` false ` .
179
+ Defaults to uncaught errors thrown in external code (these errors are handled
180
+ automatically and result in an Internal Server Error response) or runtime errors due to
181
+ developer error.
172
182
173
183
- ` files ` - file system related settings:
174
184
- ` etagsCacheMaxSize ` - sets the maximum number of file etag hash values stored in the
0 commit comments