Cheng Lou comments

Results 203 comments of


                                            Cheng Lou

Export to component(1)?

Oh, I'm talking about TJ Holowaychuk's component. https://github.com/component/component I feel like this could be a lightweight substitution for jQuery, and it's really appropriate for writing small libraries.

Faster `esy` env for global installs.

Local project development invokes this every build right? No-op bsb is 70ms. Adding 50ms for `esy refmt` during parsing is unfortunate.

Faster `esy` env for global installs.

Right, a build watcher circumvents this. I was asking about straight up `bsb -make-world`, no `-w`. Your issue makes sense.

What happens when we're pointing to a git branch that's been force pushed?

(See discord conversation) things are fixed after an `npm cache clean`. The repro is ``` "dependencies": { "reason": "facebook/reason#esy", "ocaml": "esy-ocaml/ocaml#esy" }, "peerDependencies": { "reason": "facebook/reason#esy", "ocaml": "esy-ocaml/ocaml#esy" } ```...

What happens when we're pointing to a git branch that's been force pushed?

Not sure sorry. Can't repro this anymore but people definitely reproed on other laptops.

Question: Can this be solved by including our own realpath implementation?

Doesn't our realpath compiles C++?

Changing dependency path doesn't invalidate node_modules

BTW I'm not modifying the package's content (they're symlinked and I wouldn't touch them anyway). I'm switching from a remote git url to a local one. What you said applies...

warn against incremental installs like `npm install foo` when foo isn't currently present

(Following discord discussion) Didn't know it was only true for `npm install reason` in the current setup. Though @andreypopp did say something about a general `npm install foo` too.

warn against incremental installs like `npm install foo` when foo isn't currently present

Yes, that's what I meant

warn against incremental installs like `npm install foo` when foo isn't currently present

Will I ever need to do `npm install foo`? What about in an existing project with mixed js and ocaml deps?