Paulo H. C. de Oliveira

I thank you very much for all your efforts, but I wish Next.JS would be shipped with such a thing under a `next/test-support` module. I know that I am not...

@cah-briangantzler, I tried your approach, but it didn't work for me at all. First, the result of `RestSerializer.extend({})` should be a class, right? It does not have the method `serialize`....

Thanks for your reply. I forgot it needs to be `created`, not instantitated with `new`. I will try that first. BTW, I also tried ``` import SomeSerializer from "..." ......

Unfortunately, I can not show you the repo as it is private, but using `create({})` also produced the same error: ``` const topics = schema.db.topics.where(filters); const serializer = TopicSerializer.create({}); return...

I will try to do that, but I think I won't be able to reproduce it. For example, a serializer found on `mirage/serializers/foo` should be used automatically with a model...

I am trying to specify the serializer because I gave up on figuring out why the correspondent serializer is not picked up automatically.

I could not reproduce it, @cah-briangantzler. I am sorry.

I am also facing this problem when using `$nextTick` inside a mixin. My intention was to wait for all child components to be ready in order to bind some elements...

I made a PR addressing workspaces with multiple root folders and monorepos. But I still think that the VS Code extension could be improved. For example, in my explanation about...

> You can select different projects here: > > > > would that work for you? We have an issue for updating the docs accordingly here: [microsoft/playwright.dev#747](https://github.com/microsoft/playwright.dev/issues/747) Yes, @mxschmitt, that...