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
There are quite a few build tools that have popped up in the last months. Gulp is one of them. It is based on node streams and has a very fast-growing plugin ecosystem. However, it doesn't have great metaphors for 1:n file transformations, like Sass-imports or RequireJS optimization. Because of the tree-transformations possible in Metalsmith plugins, it is a better fit for these kind of tasks.
I was wondering if it was a good idea to make Metalsmith ready for interoperation. Gulp uses Vinyl for representing files which is very similar to Metalsmith's representation. There could be a very thin adapter. Other than that Metalsmith would need a way to accept in-memory files as input instead of disk-only. For in-memory output, I made #28.
I'm curious, what you guys think.
The text was updated successfully, but these errors were encountered:
There are quite a few build tools that have popped up in the last months. Gulp is one of them. It is based on node streams and has a very fast-growing plugin ecosystem. However, it doesn't have great metaphors for 1:n file transformations, like Sass-imports or RequireJS optimization. Because of the tree-transformations possible in Metalsmith plugins, it is a better fit for these kind of tasks.
I was wondering if it was a good idea to make Metalsmith ready for interoperation. Gulp uses Vinyl for representing files which is very similar to Metalsmith's representation. There could be a very thin adapter. Other than that Metalsmith would need a way to accept in-memory files as input instead of disk-only. For in-memory output, I made #28.
I'm curious, what you guys think.
The text was updated successfully, but these errors were encountered: