got's readme should mention only setting
useElectronNetin main process, or maybe removing
remotesupport and disallowing renderer
netuse. I'd make a PR but I don't know what to do.
remotemodule, we should indeed disallow it. I commented: https://github.com/electron/electron/issues/10017#issuecomment-388627975
@sindresorhus re: an old, old chalk issue: chalk/chalk#180. I'm contributing to rollup now, and there's a small color library author going around opening a poopton of PRs on projects to swap his lib in place of chalk (advertising it as a faster drop-in replacement, which it's not). one of his selling points is the filesize. normally not a concern, but rollup is unique in that it self-rolls it and its dependencies and ships that to npm (there are a number of reasons for that). so the size was a selling point for the maintainers, as it dropped the CLI size by nearly 40kb. not sure why 40kb is exciting to anyone, but alas.
you had mentioned that
color-convert might be lazy loaded. I see that module's use has since been moved into
ansi-styles. are there any more targets for slimming down the code that'd actually be used (so it's a target for tree shaking) that you can think of, and how might one go about lazy-loading
ansi-styles these days?
as it dropped the CLI size by nearly 40kb. not sure why 40kb is exciting to anyone, but alas.
That's a silly argument...
maintainers that buy that bullshit deserve what they get
I credit them for using setPrototypeOf/proto, which I originally learned from kleur. I didn't know you had contributed that code. For that reason, I just added you to the credits in the notes.
This was actually first done in Chalk, but whatever...
into-streamwhen the stream stuff in Node.js core was completely broken and bad. It has improved a lot of recent times, so now we no longer need a wrapper module to be able to use streams.
Hi! I found a link to here from https://gist.github.com/sindresorhus/1656c46f23545deff8cc713649dcff26
I'm trying to write an eslint rule that enforces a unique string argument be sent to specific function across files. For example,
// file A fn('aStringArg') // no duplicates! // file B fn('aStringArg') // no duplicates! fn('someOtherString') // this is okay :)
My first thought was to create a Set and check against it to see if the string has been used. However, the Set never gets cleared, and if a developer deletes the duplicate arg, the original is still marked by eslint because the value remains in the Set.
Does anyone have an idea how to implement this rule?