istarkov ( Ivan Starkov )

Once u created atom definition inside component you need to share it between all components where it used using Context or props. Also instead of defining atom at place where its needed - at Component module, you need to define it now at some upper node in the tree. IMO most beauty and simplicity of idea lost :-(

istarkov

comment created time in 15 days

issue commentpmndrs/jotai

Initial atom state

On server rendering state can come and come from db etc. We can't use examples above, db state isnt known at module level and cant be cached into global vars as requests and io is processed in event loop and you cant be sure that global vars has results from current request.

istarkov

comment created time in 15 days

issue openedpmndrs/jotai

Initial atom state

Currently the most issue I see with atoms is initial atom state which especially on server cant be inside any global objects ie localStorage etc. (setEffect is not working on server too)

Creating atoms and passing them through a context - loss of main advantages (u would need to create dependent atoms in context etc)

Probably passing Provider value to atom on initial call could solve this?

I.e.

// atom already have getter fn as param so I call atom with state dependent on context subatom.

const myAtom = subatom(ctx => ctx.someVal)

....
// in some component

<InitialJotaiValueProvider value={{ someVal: 123 }}> ...

Or probably some other beautiful api can be available.

created time in 15 days

starteddai-shi/use-context-selector

started time in 23 days

startedpmndrs/jotai

started time in 23 days

startedkitten/use-editable

started time in a month

startedzhm/pg-query-parser

started time in a month

startedsdushantha/tmpmail

started time in a month

startedVMLTang/sugar-web-api

started time in a month

issue commentgoogleapis/google-auth-library-nodejs

Delegated Authentication won't work with injected Service Account on Cloud Run

Same here, what is the way to programmatically get jwt from cloudrun without credentials file or anything else. As providing securely JSON with private key needs libraries like berglas or read from secure storage

jamesvnz

comment created time in a month

issue openedgraphql/graphql-js

Performance issue with GraphQLError.js with sourcemaps enabled

This code lines https://github.com/graphql/graphql-js/blob/16009cbcb0109da03f2157a868817b886801095a/src/error/GraphQLError.js#L189-L196 cause serious performance degradation in case of node used with sourcemaps. For example dataloader fail on reading list of N nodes can cause N*100ms delay.

Explanation: Modern nodejs has sourcemaps support via --enable-source-maps flag. In current nodejs access to error.stack object is lazy, so until you read it where are no additional logic called to prepare stack traces i.e. Error.prepareStackTrace

With sourcemaps enabled node resolution algorithm for trace is not chip and on big projects costs like 100ms to build trace using sourcemaps. (see nodejs prepare stack trace)

For example on reading list of 30 items in case of dataloader fails we have 3000ms delay because of reading stack at that lines.

What are you think of making stack property lazy i.e

Object.defineProperty(this, 'stack', { get: function() {} });

This will solve performance issues and will be lazy as like as Error stack

created time in a month

issue commentgoogle-map-react/google-map-react

Drawing google.maps.Circle

Hey all this map wasnt intended to work with imperative native api, few months ago I wrote map realisation which solves issues like this and many others.

Here polygon example.

https://realadvisor.github.io/rgm/geojson

THernandez03