#wireit — Public Fediverse posts

All build systems fall down at plugins. Plugin compatibility is hard to maintain and hard to troubleshoot. Instead if tools/cli all implemented incremental builds from disc (see #typescript) to allow for fast cold starts, tools like #wireit would become our default build tools. No need for plugin bindings for a tool you want to use, just use that tools cli. @surma talked about doing something similar with bazel. I am convinced this is the correct approach.

cacheable #jest configuration using wireit. Using jestresults as output means that cacheing works regardless of args you pass. npm rest -- SomeFile will cache differently then npm test, etc
{
"wireit": {
"test": {
"command": "jest --json --outputFile jestresults.json",
"files": [
"src/**"
],
"output": [
"jestresults.json"
]
}
}
}

#JavasScript #wireit

#wireit visualizer now let's you filter the tree down by selecting a node. Helpful when you have a large complex build graph. I think I could even make this into a visual build editor.

https://github.com/deebloo/wireit-visualizer

I created a simple POC for a wireit visualizer using mermaidjs.

https://github.com/deebloo/wireit-visualizer

#node #wireit

@mattofthefuture Personally I really really like using npm workspaces and wireit. Does everything I need an nothing I don't. I used to use #lerna whenever I needed something like this. (which is now run by nx) in short workspaces handles running commands and linking and #wireit let's you create performance dependant builds. Example: https://github.com/joist-framework/joist

#wireit might be one of my favorite pieces of software in the past couple years. it does EXACTLY what I want it to do and nothing else