davidmarkclements/0x 2213
🔥 single-command flamegraph profiling 🔥
A crazy fast HTTP router
Really Fast Deep Clone
This project is a small but feature complete application build with Fastify and Svelte, and it aims to show all the core concepts of Fastify, best practices, and recommendations.
Exploring v8 performance characteristics in Node across v8 versions 5.1, 5.8, 5.9, 6.0 and 6.1
davidmarkclements/fast-safe-stringify 256
Safely and quickly serialize JavaScript objects
davidmarkclements/overload-protection 178
Load detection and shedding capabilities for http, express, restify and koa
davidmarkclements/fast-redact 158
very fast object redaction
push eventmercurius-js/cache
commit sha d355827eeeef0c337088cb36745b92d8e96d6ba8
Completed federetion support
push time in 16 hours
Pull request review commentfastify/fastify
function hasContentTypeParser (contentType) { return this[kContentTypeParser].hasParser(contentType) } +function removeContentTypeParser (contentType) {+ if (this[kState].started) {+ throw new Error('Cannot call "removeContentTypeParser" when fastify instance is already started!')+ }++ if (Array.isArray(contentType)) {+ contentType.forEach((type) => this[kContentTypeParser].remove(type))
Can you please use a for..of loop?
comment created time in 18 hours
issue commentfastify/fastify-response-validation
Support shortcut schema syntax
Would you like to send a Pull Request to address this issue? Remember to add unit tests.
comment created time in a day
issue commentpinojs/pino
`.flush()` doesn't work when pretty-print is enabled
Doc would be good, yes! Would you like to send a PR?
comment created time in a day
pull request commentmercurius-js/mercurius
Add GraphiQL request headers tab
Could you send a PR to fix this problem? Using the createFetcher should be ok.
comment created time in a day
pull request commentmercurius-js/mercurius
Add GraphiQL request headers tab
I'm not sure what credentials you are referring to.
comment created time in 2 days
push eventpinojs/pino
commit sha b5785d56a2e4ff67b3ad6948d99c01542f47d8fa
Bumped v7.0.0-rc.2
push time in 2 days
push eventpinojs/pino
commit sha 5333d73773f59331c2d5c7962dec3ee00574fc6f
Make sure that the main thread stays alive to process stdout. (#1075) * Make sure that the main thread stays alive to process stdout. This is achieved by hooking into beforeExit in on-exit-leak-free. At that point the event loop is still running so we can catch the most basic exit scenarios. However this would not work if we use `process.exit(0)` to exit the main thread. Fix #1074 * v12 support * Added docs
push time in 2 days
PR merged pinojs/pino
This is achieved by hooking into beforeExit in on-exit-leak-free.
At that point the event loop is still running so we can catch the
most basic exit scenarios. However this would not work if we use
process.exit(0) to exit the main thread.
Fix #1074
pr closed time in 2 days
issue closedpinojs/pino
Calling pino.transport() results in "Error: Not supported"
pino version: '7.0.0-rc.1'
$ cat main.js
require("pino").transport({target: "/dev/null"})
$ node main.js
events.js:187
throw er; // Unhandled 'error' event
^
Error: Not supported
at start (/Users/g.crino/pino-poc/node_modules/thread-stream/lib/worker.js:18:39)
at Object.<anonymous> (/Users/g.crino/pino-poc/node_modules/thread-stream/lib/worker.js:42:1)
at Module._compile (internal/modules/cjs/loader.js:959:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Function.Module._load (internal/modules/cjs/loader.js:727:14)
at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
at MessagePort.<anonymous> (internal/main/worker_thread.js:139:25)
at MessagePort.emit (events.js:210:5)
at MessagePort.onmessage (internal/worker/io.js:70:8)
Emitted 'error' event on ThreadStream instance at:
at /Users/g.crino/pino-poc/node_modules/thread-stream/index.js:155:16
at processTicksAndRejections (internal/process/task_queues.js:75:11)
closed time in 2 days
giuscri
pull request commentmercurius-js/mercurius
Add GraphiQL request headers tab
You can see an example implementation at https://github.com/graphql/graphiql/blob/65aa64811ccd40c5e8ba99edec825a91115a3c8b/packages/graphiql-toolkit/src/create-fetcher/lib.ts#L51-L68.
comment created time in 2 days
push eventpinojs/pino
commit sha 2d4db800586f7a483d9924c4e8864a9f24af22e0
Added docs
push time in 2 days
pull request commentpinojs/pino
Make sure that the main thread stays alive to process stdout.
Is this transparent from the library user's perspective? Or have we resurrected?:
Nope, it's totally transparent.
comment created time in 2 days
Pull request review commentpinojs/pino
Make sure that the main thread stays alive to process stdout.
+'use strict'++const { join } = require('path')+const pino = require('../..')+const transport = pino.transport({+ target: join(__dirname, 'transport-worker.js')+})+const logger = pino(transport)+logger.info('Hello')
this directory is a place for things that are run from tests. There is no other definition.
comment created time in 2 days
Pull request review commentpinojs/pino
Make sure that the main thread stays alive to process stdout.
test('pino.transport with target #pino/pretty', async ({ match, teardown }) => { const actual = await readFile(destination, 'utf8') match(strip(actual), /\[.*\] INFO.*hello/) })++test('stdout in worker', async ({ not }) => {+ let actual = ''+ const child = execa(process.argv[0], [join(__dirname, 'fixtures', 'transport-main.js')])
We place those in fixtures - they are almost all the same.
comment created time in 2 days
push eventpinojs/pino
commit sha 2d662c77779c6f56ab11c8db04074d2761e73c36
v12 support
push time in 2 days
Pull request review commentpinojs/pino
Make sure that the main thread stays alive to process stdout.
+'use strict'++const { join } = require('path')+const pino = require('../..')+const transport = pino.transport({+ target: join(__dirname, 'transport-worker.js')+})+const logger = pino(transport)+logger.info('Hello')
yes, this is called by a child process test.
comment created time in 2 days