Unlike HTTP, WebSocket communication is duplex (both the client and the server can emit and listen to events) and persistent. This difference is reflected in how one would expect to mock a WebSocket communication.
I believe mocking WebSockets should be connection-based. This way each individual connected client is scoped to a particular interceptor handler.
interceptor.on('connection', (connection) => {
This is an up-to-date guide on running Chromium in Vercel serverless functions in 2022. What you will read below is the result of two days of research, debugging, 100+ failed deployments, and a little bit of stress.
Use chrome-aws-lambda that comes with Chromium pre-configured to run in serverless, and puppeteer-core due to the smaller size of Chromium distributive.
| // TODO: make `pages` optional and measure the div when unspecified, this will | |
| // allow more normal document flow and make it easier to do both mobile and | |
| // desktop. | |
| import { | |
| createContext, | |
| useCallback, | |
| useContext, | |
| useEffect, | |
| useMemo, | |
| useRef, |
I was poking around trying to figure out all the packages I have access to publish and got curious. So I write this little script to determine the download stats for all the packages I have publish access to.
Feel free to try it yourself. Just change the username passed to getUserDownloadStats.
By default, the stats are sorted by their average daily downloads (descending). That should give you an idea of the most "popular" package of a given user relative to how long that package has been around.
You can use it with npx like so:
| // Source: https://medium.com/@minaluke/typescript-compose-function-b7512a7cc012 | |
| type ArityOneFn = (arg: any) => any | |
| type PickLastInTuple<T extends any[]> = T extends [ | |
| ...rest: infer U, | |
| argn: infer L | |
| ] | |
| ? L | |
| : never | |
| type FirstFnParameterType<T extends any[]> = Parameters<PickLastInTuple<T>>[any] | |
| type LastFnParameterType<T extends any[]> = ReturnType<T[0]> |
| declare module '*.gql' { | |
| import { DocumentNode } from 'graphql' | |
| const vaule: DocumentNode | |
| export default value | |
| } |
This document describes a flow of a request issued by different modules/libraries in NodeJS environment.
| !(A && B) // is equivalent to | |
| !A || !B | |
| !(A || B) // is equivalent to | |
| !A && !B |
If you're using Webpack to bundle your Electron app and you're getting require is not defined, and you don't want to set nodeIntegration to true for security,
change the target of your webpack bundle from electron-renderer to web. That way webpack won't be trying to
look for things like require and module in the environment.
I found this solution after reading this comment SimulatedGREG/electron-vue#644 (comment)
