Simon Fridlund

Or do you only want to circumventing before and not after for example?

To my knowledge this isn't supported. One way to achieve it is to store the handler you get when adding a hook and use that to remove the hook before...

Let's talk through a possible implementation before the PR?

Today when when you do ``` const beforeInsertPostsHandler = Posts.before.insert((...) => ...); ``` You get the handler which is an object with `remove` and `replace`, maybe we could add `collection`/`direct`...

Maybe we can support `.direct(options)`, it would be a "breaking" change but there are other potentially breaking changes in `0.9.0-rc4` so I'm thinking it's fine as long as we document...

I believe this issue might be related to [this](https://github.com/matb33/meteor-collection-hooks/blob/master/collection-hooks.js#L92), hooks are attached to different things on server and client and that might be what's causing this problem.

~~From the first code example in this issue I believe this might be related to #215.~~

- Rebased on main - Updated the spawn promise wrapper to skip the `child.on("error", ...)` part - Switched mockedExec for mockedSpawn and updated mock implementations

I'm not sure if we need to handle more cases then just "close" in the spawn promise wrapper and if we should `resolve` the promise even if there's a non-zero...

So for me in my project this works as expected. error ``` [2022-11-21T11:17:15.385Z]: Running current.sql schema-lint Connecting to undefined on undefined app_public.cars: error require-primary-key : The table app_public.cars does not...