Closed kingo55 closed 3 years ago
@kingo55 @dapperdrop I think for the most of time, we use gulp publish to publish tests we're testing in development branch, and we use Request.ly to inject the .js or .pretty.js (for me, always .pretty.js). So we can add a cli parameter to specify which type of file to publish, default is 'both'.
@allmywant
Good suggestion. I might even go further and suggest we default publish to "pretty" only. Not sure about you guys, but I exclusively use gulp && gulp publish
in my CLI for dev purposes.
When pushing something to a prod environment for clients to preview, it usually involves a merge in BitBucket or manually copy pasting into optly/convert.
@dapperdrop @allmywant - very interesting suggestions.
I think defaulting to just .pretty.js is a pretty usable default.
Been using the following pattern recently, to watch the library's files and rebuild/publish the container when anything changes:
find lib/* | entr gulp refresh
Where gulp refresh
is just build and publish running in series:
exports.refresh = gulp.series([build, publish]);
Thoughts on the naming and whether we include this in the gulp file?
@kingo55
I think gulp refresh
is fine and we should include this in the gulp file, it's very useful when we need to debug the transformation code online.
Done - closing.
When the internet is slow, your container is large or you're publishing large dev containers frequently, then
gulp publish
can be time consuming:How might we speed this process up? @allmywant @dapperdrop