Merge branch 'meteor:devel' into patch-2

This commit is contained in:
ToyboxZach
2024-01-24 09:45:05 -08:00
committed by GitHub
3 changed files with 14 additions and 6 deletions

View File

@@ -10,7 +10,7 @@
[![Travis CI Status](https://api.travis-ci.com/meteor/meteor.svg?branch=devel)](https://app.travis-ci.com/github/meteor/meteor)
[![CircleCI Status](https://circleci.com/gh/meteor/meteor.svg?style=svg)](https://app.circleci.com/pipelines/github/meteor/meteor?branch=devel)
[![built with Meteor](https://img.shields.io/badge/Meteor-2.13.3-green?logo=meteor&logoColor=white)](https://meteor.com)
[![built with Meteor](https://img.shields.io/badge/Meteor-2.14-green?logo=meteor&logoColor=white)](https://meteor.com)
</div>
@@ -46,7 +46,7 @@ Use the same code whether youre developing for web, iOS, Android, or desktop
# 🔥 Getting Started
How about trying a getting started tutorial in your favorite technology?
How about trying a tutorial to get started with your favorite technology?
| [<img align="left" width="25" src="https://upload.wikimedia.org/wikipedia/commons/a/a7/React-icon.svg"> React](https://react-tutorial.meteor.com/) |
| - |

View File

@@ -7,7 +7,7 @@ description: How to migrate your application to Meteor 3.0.
## What's the status of version 3.0?
**Latest version:** `3.0-alpha.20` <br/>
**Latest version:** `3.0-beta.0` <br/>
**Node.js version:** `20.9.0 LTS`
Meteor 3.0 is in alpha and not recommended for production. You can check the "[Release 3.0 Pull Request](https://github.com/meteor/meteor/pull/12359)" to see what is being changed.
@@ -112,7 +112,7 @@ findOne is not available on the server. Please use findOneAsync instead.
You can create a new Meteor 3.0 project by running the command below:
```bash
meteor create my-new-project --release 3.0-alpha.20
meteor create my-new-project --release 3.0-beta.0
```
### How to update from version 2?
@@ -120,7 +120,7 @@ meteor create my-new-project --release 3.0-alpha.20
You can update your Meteor 2.x project by running the command below inside your project folder:
```bash
meteor update --release 3.0-alpha.20
meteor update --release 3.0-beta.0
```
### How to follow the progress on version 3?
@@ -143,7 +143,7 @@ The migration will look like this:
```js
// in you package.js
Package.onUse((api) => {
api.versionsFrom(['1.10', '2.3', '3.0-alpha.20']);
api.versionsFrom(['1.10', '2.3', '3.0-beta.0']);
// ^^^^^^^ for testing your package with meteor 3.0
api.versionsFrom(['1.10', '2.3', '3.0']);

View File

@@ -296,6 +296,14 @@ Package.onTest(function(api) {
From within your test entry point, you can import other files as you would in the package proper.
You can also use [`mtest`](https://github.com/zodern/mtest) to test your packages like so:
```bash
mtest --package ./ --once 2.14
```
Which helps immensely if you'd like to test your package in CI/CD setup. You can see an example [here](https://github.com/monti-apm/monti-apm-agent/blob/master/.github/workflows/test.yml).
You can read more about testing in Meteor in the [Testing article](testing.html).
<h2 id="publishing-atmosphere">Publishing your package</h2>