Merge branch 'devel' into fix/14013

Author: nachocodoner

docs/source/commandline.md

@@ -677,7 +677,7 @@ Your project should be a git repository as the commit hash is going to be used t
 The `cache-build` option is available since Meteor 1.11.
 {% endpullquote %}
 
-With the argument `--container-size` you can change your app's container size using the deploy command. The valid arguments are: `tiny`, `compact`, `standard`, `double`, `quad`, `octa`, and `dozen`. One more thing to note here is that the `--container-size` flag can only be used when the `--plan` option is already specified, otherwise using the `--container-size` option will throw an error with the message : `Error deploying application: Internal error`. To see more about the difference and prices of each one you can check [here](https://www.meteor.com/cloud#pricing-section).
+With the argument `--container-size` you can change your app's container size using the deploy command. The valid arguments are: `tiny`, `compact`, `standard`, `double`, `quad`, `octa`, and `dozen`. One more thing to note here is that the `--container-size` flag can only be used when the `--plan` option is already specified, otherwise using the `--container-size` option will throw an error with the message : `Error deploying application: Internal error`. To see more about the difference and prices of each one you can check [here](https://galaxycloud.app/meteorjs/pricing).
 
 {% pullquote warning %}
 The `--container-size` option is available since Meteor 2.4.1.

guide/source/deployment.md

@@ -194,7 +194,7 @@ MONGO_URL=mongodb://localhost:27017/myapp ROOT_URL=http://my-app.com PORT=3000 n
 ```
 
 * `ROOT_URL` is the base URL for your Meteor project
-* `PORT` is the port at which the application is running 
+* `PORT` is the port at which the application is running
 * `MONGO_URL` is a [Mongo connection string URI](https://docs.mongodb.com/manual/reference/connection-string/) supplied by the MongoDB provider.
 
 
@@ -322,7 +322,7 @@ Galaxy's UI provides a detailed logging system, which can be invaluable to deter
 
 If you really want to understand the ins and outs of running your Meteor application, you should use an Application Performance Monitoring (APM) service. There are multiple services designed for Meteor apps:
 
-- [Meteor APM](https://www.meteor.com/cloud)
+- [Meteor APM](https://galaxycloud.app/)
 - [Monti APM](https://montiapm.com/)
 - [Meteor Elastic APM](https://github.com/Meteor-Community-Packages/meteor-elastic-apm)
 

guide/source/performance-improvement.md

@@ -11,9 +11,9 @@ Meteor supports many view layers.
 The most popular are:
 - [React](react.html): official [page](http://reactjs.org/)
 - [Blaze](blaze.html): official [page](http://blazejs.org/)
-- [Angular](http://www.angular-meteor.com): official [page](https://angular.io/)
+- [Angular](angular.html): official [page](https://angular.io/)
 - [Vue](vue.html): official [page](https://vuejs.org/)
-- [Svelte](https://www.meteor.com/tutorials/svelte/creating-an-app): official [page](https://svelte.dev/)
+- [Svelte](svelte.html): official [page](https://svelte.dev/)
 
 If you are starting with web development we recommend that you use Blaze as it's very simple to learn.
 

guide/source/ui-ux.md

@@ -56,7 +56,7 @@ meteor
 
 Building an application with Meteor?
 
-* Deploy on Galaxy hosting: https://www.meteor.com/cloud
+* Deploy on Galaxy hosting: https://galaxycloud.app/
 * Announcement list: sign up at https://www.meteor.com/
 * Discussion forums: https://forums.meteor.com/
 * Join the Meteor community Slack by clicking this [invite link](https://join.slack.com/t/meteor-community/shared_invite/enQtODA0NTU2Nzk5MTA3LWY5NGMxMWRjZDgzYWMyMTEyYTQ3MTcwZmU2YjM5MTY3MjJkZjQ0NWRjOGZlYmIxZjFlYTA5Mjg4OTk3ODRiOTc).

npm-packages/eslint-plugin-meteor/README.md

@@ -360,7 +360,7 @@ Or see the docs at:
 
 Deploy and host your app with Cloud:
 
-  www.meteor.com/cloud
+  https://galaxycloud.app/
 
 ***************************************
 You might need to open a new terminal window to have access to the meteor command, or run this in your terminal:

npm-packages/meteor-installer/install.js

@@ -1125,7 +1125,7 @@ main.registerCommand({
       "If you are new to Meteor, try some of the learning resources here:"
     );
     Console.info(
-      Console.url("https://www.meteor.com/tutorials"),
+      Console.url("https://docs.meteor.com/"),
       Console.options({ indent: 2 })
     );
 
@@ -1134,7 +1134,7 @@ main.registerCommand({
       "When you’re ready to deploy and host your new Meteor application, check out Cloud:"
     );
     Console.info(
-      Console.url("https://www.meteor.com/cloud"),
+      Console.url("https://galaxycloud.app/"),
       Console.options({ indent: 2 })
     );
 

tools/cli/commands.js

@@ -126,7 +126,7 @@ export default defineConfig({
         ],
       },
       { text: "API", link: "/api/" },
-      { text: "Galaxy Cloud", link: "https://www.meteor.com/cloud" },
+      { text: "Galaxy Cloud", link: "https://galaxycloud.app" },
       {
         text: metadata.currentVersion,
         items: metadata.versions.reverse().map((v) => {
@@ -490,11 +490,11 @@ export default defineConfig({
             link: "/tutorials/vue/meteorjs3-vue3-vue-meteor-tracker",
             text: "Meteor + Vue + vue-meteor-tracker",
           },
-          {           
+          {
             text: "Meteor.js 3 + Solid",
             link: "/tutorials/solid/index",
           },
-          { 
+          {
             text: "Meteor.js 3 + Blaze",
             link: "/tutorials/blaze/index",
           },

v3-docs/docs/.vitepress/config.mts

@@ -30,7 +30,7 @@ Meteor.startup(async () => {
   if ((await LinksCollection.find().countAsync()) === 0) {
     await LinksCollection.insertAsync({
       title: "Do the Tutorial",
-      url: "https://www.meteor.com/tutorials/react/creating-an-app",
+      url: "https://docs.meteor.com/tutorials/react",
     });
   }
 });
@@ -148,10 +148,7 @@ import { Meteor } from "meteor/meteor";
 
 function Component() {
   const addLink = () =>
-    Meteor.callAsync(
-      "addLink",
-      "https://www.meteor.com/tutorials/react/creating-an-app"
-    );
+    Meteor.callAsync("addLink", "https://docs.meteor.com/tutorials/react/");
 
   return (
     <div>
@@ -398,7 +395,6 @@ even if the method's writes are not available yet, you can specify an
 Use `Meteor.call` only to call methods that do not have a stub, or have a sync stub. If you want to call methods with an async stub, `Meteor.callAsync` can be used with any method.
 :::
 
-
 <ApiBox name="Meteor.callAsync" />
 
 `Meteor.callAsync` is just like `Meteor.call`, except that it'll return a promise that you need to solve to get the server result. Along with the promise returned by `callAsync`, you can also handle `stubPromise` and `serverPromise` for managing client-side simulation and server response.
@@ -409,64 +405,63 @@ The following sections guide you in understanding these promises and how to mana
 
 ```javascript
 try {
-	await Meteor.callAsync('greetUser', 'John');
-	// 🟢 Server ended with success
-} catch(e) {
-	console.error("Error:", error.reason); // 🔴 Server ended with error
+  await Meteor.callAsync("greetUser", "John");
+  // 🟢 Server ended with success
+} catch (e) {
+  console.error("Error:", error.reason); // 🔴 Server ended with error
 }
 
-Greetings.findOne({ name: 'John' }); // 🗑️ Data is NOT available
+Greetings.findOne({ name: "John" }); // 🗑️ Data is NOT available
 ```
 
 #### stubPromise
 
 ```javascript
-await Meteor.callAsync('greetUser', 'John').stubPromise;
+await Meteor.callAsync("greetUser", "John").stubPromise;
 
 // 🔵 Client simulation
-Greetings.findOne({ name: 'John' }); // 🧾 Data is available (Optimistic-UI)
+Greetings.findOne({ name: "John" }); // 🧾 Data is available (Optimistic-UI)
 ```
 
 #### stubPromise and serverPromise
 
 ```javascript
-const { stubPromise, serverPromise } = Meteor.callAsync('greetUser', 'John');
+const { stubPromise, serverPromise } = Meteor.callAsync("greetUser", "John");
 
 await stubPromise;
 
 // 🔵 Client simulation
-Greetings.findOne({ name: 'John' }); // 🧾 Data is available (Optimistic-UI)
+Greetings.findOne({ name: "John" }); // 🧾 Data is available (Optimistic-UI)
 
 try {
   await serverPromise;
   // 🟢 Server ended with success
-} catch(e) {
+} catch (e) {
   console.error("Error:", error.reason); // 🔴 Server ended with error
 }
 
-Greetings.findOne({ name: 'John' }); // 🗑️ Data is NOT available
+Greetings.findOne({ name: "John" }); // 🗑️ Data is NOT available
 ```
 
 #### Meteor 2.x contrast
 
 For those familiar with legacy Meteor 2.x, the handling of client simulation and server response was managed using fibers, as explained in the following section. This comparison illustrates how async inclusion with standard promises has transformed the way Meteor operates in modern versions.
 
-``` javascript
-Meteor.call('greetUser', 'John', function(error, result) {
+```javascript
+Meteor.call("greetUser", "John", function (error, result) {
   if (error) {
     console.error("Error:", error.reason); // 🔴 Server ended with error
   } else {
     console.log("Result:", result); // 🟢 Server ended with success
   }
 
-  Greetings.findOne({ name: 'John' }); // 🗑️ Data is NOT available
+  Greetings.findOne({ name: "John" }); // 🗑️ Data is NOT available
 });
 
 // 🔵 Client simulation
-Greetings.findOne({ name: 'John' }); // 🧾 Data is available (Optimistic-UI)
+Greetings.findOne({ name: "John" }); // 🧾 Data is available (Optimistic-UI)
 ```
 
-
 <ApiBox name="Meteor.apply" />
 
 `Meteor.apply` is just like `Meteor.call`, except that the method arguments are
@@ -504,8 +499,6 @@ different collections. We hope to lift this restriction in a future release.
 
 </ApiBox>
 
-
-
 ```js
 import { Meteor } from "meteor/meteor";
 import { check } from "meteor/check";