Update new-compiler.md

Author: GarboMuffin

docs/website/new-compiler.md

@@ -13,7 +13,7 @@ This is the largest single change we've ever made. We've tried to test it thorou
 The new compiler breaks a small handful of custom extensions. See the [extensions](#extensions) section below for details and workarounds.
 :::
 
-The new compiler is currently only available on the website. The packager, desktop app, and other experiment branches will be updated later.
+The new compiler is currently used on the website and the packager. It will be included in the next update of TurboWarp Desktop (v1.15.0).
 
 ## Performance comparison {#performance}
 
@@ -74,6 +74,8 @@ All extensions included in the TurboWarp extension list will work the same, and
 
 A small handful of custom extensions use an API called `i_will_not_ask_for_help_when_these_break` to integrate more directly with the compiler. We gave this API that crazy name because we knew it was going to break at some point, and we didn't want a small handful of extensions to restrict us from being able to change the compiler's internals when needed. If your project requires these extensions, you can use https://experiments.turbowarp.org/old-compiler/ instead until extensions become compatible.
 
+If you also need to package your project, you can use https://packager-legacy.turbowarp.org/old-compiler/.
+
 ## Brief technical overview {#technical-overview}
 
 The broad idea is that the compiler analyzes scripts to determine what kinds of values each variable may have at each point in the script. This allows it to remove unnecessary type conversions and generate more specialized code. The old compiler tried to do this too, but was unable to reason about loops or conditionals.