Creating custom SolidJS hook that can be used in a global scope

Need some help understanding how to build a custom SolidJS hook that can be used both locally inside a component and outside in the global scope (like

createSignal

createSignal

can).

Below is. a small snippet of a custom hook I am writing:

export function createDatabase(dbOrName?: string | Database, config: ConfigOpts = {}): CreateDatabase {

  const database = createMemo(() => (isDatabase(dbOrName) ? dbOrName : genDb(dbOrName || "DefaultDB", config)));

return { database }

export function createDatabase(dbOrName?: string | Database, config: ConfigOpts = {}): CreateDatabase {

  const database = createMemo(() => (isDatabase(dbOrName) ? dbOrName : genDb(dbOrName || "DefaultDB", config)));

return { database }

The question I have is around the floating

createMemo

createMemo

that I use in the implementation. When I use the

createDatabase

createDatabase

hook globally, I get greeted with the console warning:

computations created outside a 'createRoot' or 'render' will never be disposed

computations created outside a 'createRoot' or 'render' will never be disposed

I'm not familiar with how to properly address that warning and hoping the community can offer some guidance here.

Brendonovich•1/27/24, 2:58 AM

This part of the tutorial should help: https://www.solidjs.com/tutorial/stores_nocontext

SolidJS

Solid is a purely reactive library. It was designed from the ground up with a reactive core. It's influenced by reactive principles developed by previous libraries.

Brendonovich•1/27/24, 2:59 AM

Namely wrap your memo in

danchezOP•1/27/24, 3:01 AM

Ah, excellent. It's either that or I wrap the entire export of my function in a is another option as well correct?

Brendonovich•1/27/24, 3:02 AM

Yeah that's also an option

Brendonovich•1/27/24, 3:02 AM

Ah actually maybe no

Brendonovich•1/27/24, 3:02 AM

As long as the

createMemo

createMemo

is inside the you can do whatever else you want

danchezOP•1/27/24, 3:04 AM

Gotcha -- so it seems I can take one of those two approaches. Really appreciate the insight!! Thank you!

Brendonovich•1/27/24, 3:04 AM

No worries, all you're really doing is silencing the warning

Brendonovich•1/27/24, 3:04 AM

The

createMemo

createMemo

will still never be disposed since you don't manually dispose the root

Brendonovich•1/27/24, 3:04 AM

But that's your intended behaviour

danchezOP•1/27/24, 3:05 AM

Are there any potential downside to use hooks in a global manner for SPAs?

Brendonovich•1/27/24, 3:05 AM

Not that I'm aware of

Brendonovich•1/27/24, 3:06 AM

Testability may be one

danchezOP•1/27/24, 3:06 AM

Ah, yeah, I can see that becoming a problem for sure

danchezOP•1/27/24, 3:07 AM

Good call

Alex Lohr•1/27/24, 8:59 AM

We have renderHook in , so testability should be covered.