To be honest, I think it's a bit too complicated

[hairyf]

The plugin I envisioned should be simple and easy to use

import { proxy } from "valtio-plugin"
import { subscribe, ... } from "valtio/vanilla"
import { devtools } from 'valtio/utils';

function plugin(options) {
  return (state) => {
    // init
    // subscribe(change)
    // ...
    return () => {} // dispose(optional)
  }
}

proxy.use(globalPlugin({...}))

const instance = proxy.createInstance()

instance.use(plugin)

const state = instance({...})

devtools(state)

I know this will lose a lot of state handling, but the question is, do we need so many methods

I noticed that many interception operations have been implemented in the source code. Will this affect the stability of the framework?

[overthemike]

I appreciate the feedback.

I should probably document how to use this a bit better. The only time you would need to use proxy.createInstance is if they only want the plugin to apply to that instance and not others. If they want to apply it to their entire state, the end user's code would look something like this:

import { proxy } from 'valtio-plugin'
import { someGlobalPlugin } from 'some-global-plugin'

proxy.use(someGlobalPlugin({...})

valtio provides methods like unstable_replaceInternalFunction and unstable_getInternalState. While this allows for customization of valtio functionality, it will also apply that functionality globally if not reset and managed properly. As far as the methods that are available, those methods are for plugin authors, not the plugin users.

Can you expand on your stability of the framework question? This is deliberately separate from valtio core so it won't ever effect the core library. I might not be understanding what you're asking though...

[hairyf]

sorry, I’m actually not familiar with unstable_replaceInternalFunction or unstable_getInternalState at all—these APIs don't even appear in the official documentation. To be honest, I don't really care whether they are technically "safe" or not (and sorry again hh); I’m just concerned because valtio-plugin relies on a lot of "invisible magic" that can be quite confusing for developers don't have a deep internal understanding of Valtio(like me who).

In add. i personally prefer simple APIs that reduce my cognitive load. I just wanted to share my thought process: when I first saw valtio-plugin, I went from "Damn, we finally have official plugin support! I have to try this" to "Wait, this is so complex... there are nearly 10 to 20 different APIs. Never mind."