This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• chore(deps): update dependency @types/lodash.clone to v4.5.7
• chore(deps): update dependency del-cli to v3.0.1
• chore(deps): update dependency husky to v4.3.8
• chore(deps): update dependency lint-staged to v10.5.4
• chore(deps): update dependency ts-jest to v28.0.8
• chore(deps): update dependency typescript to v4.9.5
• chore(deps): update react monorepo to v18.0.28 (@types/react, @types/react-dom)
• chore(deps): update dependency @hoishin/prettierrc to v2.2.0
• chore(deps): update dependency @hoishin/tsconfig to v2.1.0
• chore(deps): update dependency @types/node to v12.20.55
• chore(deps): update dependency eslint-config-hoishin to v0.4.2
• chore(deps): update dependency prettier to v2.8.7
• chore(deps): update dependency sort-package-json to v1.57.0
• fix(deps): update dependency tslib to v2.5.0
• chore(deps): update actions/checkout action to v3
• chore(deps): update actions/setup-node action to v3
• chore(deps): update dependency @testing-library/react to v14
• chore(deps): update dependency @types/node to v18
• chore(deps): update dependency del-cli to v5
• chore(deps): update dependency eslint to v8
• chore(deps): update dependency husky to v8
• chore(deps): update dependency lint-staged to v13
• chore(deps): update dependency nodecg to v2
• chore(deps): update dependency sort-package-json to v2
• chore(deps): update dependency standard-version to v9
• chore(deps): update dependency typescript to v5
• chore(deps): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• 🔐 Create all pending approval PRs at once 🔐

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

There is useListenFor hook but it's really a basic hook that only registers a callback to nodecg.listenFor.

It would be nice to receive feedback and use cases so it can be more useful.

Giving a simple example of what I'm trying to do:

function Timing() {
  const [count, setCount] = useReplicant("counter");
  return (
    <div>
      <div>{count.length}</div>
      <button onClick={() => setCount([count[0] + 1])} />
    </div>
  );
}

setCount returns an array containing a cell containing the number 1.

I'm getting Cannot read properties of undefined (reading 'length') I understand where this is coming from.

I've tried setting setCount([]) directly after the const = ... before the return (...)

I tried what previously worked const [count, setCount] = useReplicant("counter", []);
I'm not sure what the correct way to set this up is, it worked previously before doing a dependency and node update.

Totally understand this is in ALPHA and asking questions is probably not helpful, but as a point of feedback, If I can't set a default value or object it's a bit useless.

I read through the src of useReplicant and couldn't workout the new way to pass in a default value/object to the Rep.

Node20 - LTS
react - 18
nodecg - latest
@nodecg-react-hooks - latest

happy to list any thing else needed but I believe these are the minimum required to cause an error.

I think this library has been around long enough and used enough that it could be made into v1.0 and live on the NodeCG org instead of here. Up to you, though!

useSomething is a conventional name for hooks, but it's not ideal for npm package names because of vagueness. There are number of options but I'm leaning to @nodecg/react-hooks

The plugin is pretty much a must when writing React hooks.

react-testing-library has been moved to @testing-library/react.

ref: #21

nodecg.Replicant has a 2nd optional parameter for namespace. Unfortunately, the bundle I'm working with uses it exclusively. See: https://nodecg.com/NodeCG.html#Replicant

I did make a quick version of useReplicantNS as a workaround, but would rather get something into your main repository. I didn't know if maybe adding it to the options and taking it out if it exists is better for your API than making a whole new method.

I'm willing to make and submit the change, but I didn't want to do extra work that you might want to do differently anyway.

Thanks. Great work so far!

An example with useState and useReplicant:

const [data, setData] = React.useState(0);
setData(previousData => previousData + 1);

const [replicant, setReplicant] = useReplicant(0);
setReplicant(previousData => previousData + 1); // this is not supported!

Would be great if that was supported, because old values could be captured when using useEffect for example.

Currently, swapping out the namespace using a prop does not cause useReplicant to use the new replicant name. My suspicion is that its because the internal useEffect never runs on subsequent re-renders.

Here's a gist where this problem manifests. The "OBSControlView" object always binds to the first namespace, even if the prop changes.

https://gist.github.com/CarlosFdez/ab3ab575a62c048daacb8f6b38a6f2d3

My suggestion is to add repName as a param to line 39. I wanted to ask here for the go-ahead before doing it.

It currently has no unit test since I couldn't find a good way to write one when I initially made this library, but it really needs tests.

I have skeleton tests unfinished that can be a starting point.