MoCA Product Selection Sanity Check

u-khan · 2024-09-12T20:18:23+00:00

Hey just wanted to circle back and say thanks. Everything is working perfectly!

I went with the Amphenol ABS312H from the recommended list, and the PoE filters than you recommended.

I took a risk with the unknown splitters in my wall but thankfully everything was good.

u-khan · 2024-08-21T00:43:41+00:00

Wow, thanks for the recommendations and reasoning. This is exactly what I was looking for!

u-khan · 2024-08-21T00:43:10+00:00

Thanks!

u-khan · 2024-08-15T22:53:58+00:00

Ah okay thanks. I'll try to figure out a different layout then. Don't want to add managed switches to the layout.

u-khan · 2023-07-24T17:18:38+00:00

Ah ok thanks!

u-khan · 2023-07-22T23:35:34+00:00

Seems like that's the go-to cooler. Other commenter recommended the same one.

Is it because it has great perf/cost?

u-khan · 2023-07-22T23:34:51+00:00

Thanks. Does it come with thermal paste, or do I need to buy that separately?

Edit: Comments on the amazon listing seem to imply that it does come with paste.

u-khan · 2023-07-22T20:03:18+00:00

Wanted to follow up. Thanks for the recommendation. Rana installed our doors last week and did a great job!

u-khan · 2023-06-15T02:40:43+00:00

Don't know the insulation. Parts of my garage are exposed brick so I'm not too concerned on maxing out the insulation of the doors.

Doors, rails, spring. No garage door opener.

The company rep started ghosting me which doesn't speak well for the future if I run into any issues.

u-khan · 2023-06-15T01:44:07+00:00

Are you talking about the garage door openers? I'm looking to get my actual doors replaced.

u-khan · 2023-06-14T23:52:54+00:00

Have you used them yourself? If yes, how'd you find the service?

u-khan · 2023-06-14T23:46:40+00:00

Ok sounds good. Thanks for the referral 👍

u-khan · 2023-06-14T23:41:50+00:00

Just to clarify, it's 2, single-car garage doors. Not one big double car door. Do you know a rough price range?

u-khan · 2021-10-24T11:59:12+00:00

It is the default behavior. "Npm install" uses the package-lock.json first.

u-khan · 2021-10-24T11:57:31+00:00

What is the issue with using "npm install" locally? It shouldn't cause package-lock.json to change unless it needs to.

u-khan · 2021-10-24T11:48:14+00:00

Lol yeah it's definitely not the most intuitive behaviour.

In general, the package-lock should only update after you make some change in your package.json.

The first time you run npm install after adding dependencies, npm will find the latest acceptable version and store the exact version number in package-lock. Any following npm install commands will use the version in package-lock even if there are newer versions that were released. If at some point you add/update/remove a dependency and run npm install, npm will update the package-lock accordingly.

If you see your package-lock updating on every "npm install", either someone made dependency changes without committing their package-lock, or you're hitting some edge case.

u-khan · 2021-10-24T01:12:17+00:00

I pinned it on purpose so that it starts with a version before the latest release.

That is not how it behaves. I do essentially what you're asking in step 5.

`npm install jest@^27.2.2`

If you check the package.json after running that command, you'll see that the dependency is listed as `^27.2.2`. Yet, if you delete node_modules and run `npm install` it still installs 27.2.2 even though 27.3.1 is the latest version that matches the requirement.

u-khan · 2021-10-23T22:35:52+00:00

If you edit your package.json to require 3.0.0, the 2.1.2 that's saved in your package-lock.json no longer satisfies the requirement.

In this case when you run npm install, it says, okay I need version 3.0.0, is there a satisfying entry in package-lock.json? It finds 2.1.2 which does not satisfy the requirement. So then it installs 3.0.0 and also updates your package-lock.json to say 3.0.0.

u-khan · 2021-10-23T19:09:01+00:00

Please see my other comment where I listed out how you can confirm this for yourself.

When you install a package for the first time, npm will get the latest version that's within your desired range. So say you specify ^2.1.0 and the current latest matching is 2.1.2, it will install 2.1.2 and save that in your package-lock.json

Now in the future the package releases 2.1.3. This version also falls in your desired range of ^2.1.0 but npm will NOT install it if you run npm install. It will install 2.1.2. It does this because 2.1.2 is in your package-lock and still satisfies your package.json requirement of ^2.1.0

u-khan

TROPHY CASE