Include build id in welcome notebun-v0.0.0-9bun-v0.0.0-8bun-v0.0.0-10

5 files changed, 24 insertions, 7 deletions

diff --git a/Makefile b/Makefile
index e35fe3809..e6173bd17 100644
--- a/Makefile
+++ b/Makefile
@@ -11,7 +11,7 @@ sign-macos-x64:
 sign-macos-aarch64: 
 	gon sign.macos-aarch64.json
 
-release-macos-x64: build-obj jsc-bindings-mac bun-link-lld-release sign-macos-x64
+release-macos-x64: build-obj jsc-bindings-mac bun-link-lld-release sign-macos-x64 release-macos-x64-push
 release-macos-aarch64: build-obj jsc-bindings-mac bun-link-lld-release sign-macos-aarch64
 
 api: 
@@ -37,10 +37,25 @@ jsc-bindings-headers:
 	mkdir -p src/JavaScript/jsc/bindings-obj/
 	zig build headers
 
-bump: 
+BUILD_ID := $(shell cat ./build-id)
+
+bump-build-id: 
 	expr $(BUILD_ID) + 1 > build-id
 
-BUILD_ID := $(shell cat ./build-id)
+BUN_BUILD_TAG := bun-build-$(BUILD_ID)
+
+tag: 
+	git tag $(BUN_BUILD_TAG)
+	git push --tags
+
+prepare-release: bump-build-id tag release-create
+
+release-create:
+	gh release create --title "Bun - build $(BUILD_ID)" "$(BUN_BUILD_TAG)"
+
+release-macos-x64-push:
+	gh release upload $(BUN_BUILD_TAG) --clobber release/bun-macos-x64.zip
+
 
 jsc-copy-headers:
 	find src/JavaScript/jsc/WebKit/WebKitBuild/Release/JavaScriptCore/Headers/JavaScriptCore/ -name "*.h" -exec cp {} src/JavaScript/jsc/WebKit/WebKitBuild/Release/JavaScriptCore/PrivateHeaders/JavaScriptCore \;
diff --git a/README.md b/README.md
index a455e36b5..e6b8efbb4 100644
--- a/README.md
+++ b/README.md
@@ -117,13 +117,15 @@ Bun is a project with incredibly large scope, and it's early days.
 
 Bun is great for building websites & webapps. For libraries, consider using Rollup or esbuild instead. Bun currently doesn't minify code and Bun's dead code elimination doesn't look beyond the current file.
 
-Bun is focused on:
+Today, Bun is focused on:
 
 - Development, not production
 - Compatibility with existing frameworks & tooling
 
 Ideally, most projects can use Bun with their existing tooling while making few changes to their codebase. That means using Bun in development, and continuing to use Webpack, esbuild, or another bundler in production. Using two bundlers might sound strange at first, but after all the production-only AST transforms, minification, and special development/production-only imported files...it's not far from the status quo.
 
+Longer-term, Bun intends to replace Node.js, Webpack, Babel, and PostCSS (in production).
+
 # Configuration
 
 ### Loaders
diff --git a/build-id b/build-id
index 45a4fb75d..301160a93 100644
--- a/build-id
+++ b/build-id
@@ -1 +1 @@
-8
+8
\ No newline at end of file
diff --git a/src/global.zig b/src/global.zig
index 55ffbc55b..5871d3ba3 100644
--- a/src/global.zig
+++ b/src/global.zig
@@ -384,7 +384,7 @@ pub const Output = struct {
 };
 
 pub const Global = struct {
-    pub const build_id = std.fmt.parseInt(u64, @embedFile("../build-id"), 10) catch unreachable;
+    pub const build_id = std.fmt.parseInt(u64, std.mem.trim(u8, @embedFile("../build-id"), "\n \r\t"), 10) catch unreachable;
 
     pub fn panic(comptime fmt: string, args: anytype) noreturn {
         @setCold(true);
diff --git a/src/http.zig b/src/http.zig
index b6a14357b..40e828245 100644
--- a/src/http.zig
+++ b/src/http.zig
@@ -2553,7 +2553,7 @@ pub const Server = struct {
             }
         } else {
             if (server.bundler.options.routes.single_page_app_routing) {
-                Output.prettyError(" Bun!!<r>\n\n\n<d>  Link:<r> <b><cyan>http://{s}<r>\n       <d>./{s}/index.html<r> \n\n\n", .{
+                Output.prettyError(" Bun!! <d>build {d}<r>\n\n\n<d>  Link:<r> <b><cyan>http://{s}<r>\n       <d>./{s}/index.html<r> \n\n\n", .{
                     Global.build_id,
                     addr,
                     resolve_path.relative(server.bundler.fs.top_level_dir, server.bundler.options.routes.static_dir),