You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm going to create an HTTP API that can poll to get status of watch-fs plugin, if it returns true, then in the browser, we invoke a sync from the server to the browser. Otherwise we wait a while.
The text was updated successfully, but these errors were encountered:
that short circuit the incoming request, it will match all the request url that is without "/", so if user defined route is without "/", then it will be ignored.
So the solution is simple:
Use /linonetwo/watch-fs-can-sync instead of /watch-fs-can-sync
Describe the bug
I've created a custom route:
get-can-sync.js
With
get-can-sync.js.meta
But
111
is logged,222
is never logged.To Reproduce
Steps to reproduce the behavior:
get-can-sync.js
andget-can-sync.js.meta
Expected behavior
I can write my custom route in my plugin.
Desktop (please complete the following information):
Additional context
I've created a watch-fs plugin #3060 (comment)
I'm going to create an HTTP API that can poll to get status of watch-fs plugin, if it returns true, then in the browser, we invoke a sync from the server to the browser. Otherwise we wait a while.
The text was updated successfully, but these errors were encountered: