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
While trying to implement a small custom little wrapper around Remix, I found some limitations with the cli API. While we can manage with the build and some sync code, it becomes more difficult or inconvenient when dealing with watch or dev.
I know that right now, the team doesn't want to open the compiler to the outside in order to avoid possible problems or complex logic creeping into the codebase. Nonetheless, I really think that a good compromise would be to allow the WatchCallbacks to be async in order to allow for minimal interop with the Remix compiler.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
While trying to implement a small custom little wrapper around Remix, I found some limitations with the
cli
API. While we can manage with thebuild
and somesync
code, it becomes more difficult or inconvenient when dealing withwatch
ordev
.I know that right now, the team doesn't want to open the compiler to the outside in order to avoid possible problems or complex logic creeping into the codebase. Nonetheless, I really think that a good compromise would be to allow the
WatchCallbacks
to beasync
in order to allow for minimal interop with the Remix compiler.At the same time, it might be worth it, to allow such callbacks to be passed into the
dev
command as well 🙏Beta Was this translation helpful? Give feedback.
All reactions