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 debugging a library that can either be used on a browser or on Node. However, there's a few problems:
gobble serve builds and serves files in .gobble on localhost:4567. However, due to the variable directory structure, it's not easy for node scripts to consume that built library.
gobble watch out watches files and builds to an out directory. This option is easier for node, as the directory is in a predictable path. However, the files aren't served by a server for the browser.
Separately, they're fine. But it's quite annoying to stop the gobble serve and run gobble watch for node, and vice versa to check if the library works fine on both environments. Is it possible to merge functionality? Like a command that builds to a predictable directory and serve from that directory?
The text was updated successfully, but these errors were encountered:
I'm debugging a library that can either be used on a browser or on Node. However, there's a few problems:
gobble serve
builds and serves files in.gobble
onlocalhost:4567
. However, due to the variable directory structure, it's not easy for node scripts to consume that built library.gobble watch out
watches files and builds to anout
directory. This option is easier for node, as the directory is in a predictable path. However, the files aren't served by a server for the browser.Separately, they're fine. But it's quite annoying to stop the gobble serve and run gobble watch for node, and vice versa to check if the library works fine on both environments. Is it possible to merge functionality? Like a command that builds to a predictable directory and serve from that directory?
The text was updated successfully, but these errors were encountered: