github/meteor
1
1
Fork 0
mirror of https://github.com/meteor/meteor.git synced 2026-01-09 07:38:15 -05:00
Code Issues Packages Projects Releases Wiki Activity

Meteor v3 docs for Solid tutorial

Browse Source
This commit is contained in:
Aaron Rosenzweig
2025-10-26 16:28:24 -04:00
committed by Italo José
parent 6f48b86603
commit 933c7b30d0
31 changed files with 1965 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
v3-docs/docs/.vitepress/config.mts
View File

@@ -40,6 +40,10 @@ export default defineConfig({
text: "Meteor + Vue + vue-meteor-tracker",
link: "/tutorials/vue/meteorjs3-vue3-vue-meteor-tracker",
},
{
text: "Meteor.js 3 + Solid",
link: "/tutorials/solid/index",
},
{
link: "/tutorials/application-structure/index",
text: "Application structure",
@@ -472,6 +476,10 @@ 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",
},
{
link: "/tutorials/application-structure/index",
text: "Application structure",

200
v3-docs/docs/tutorials/solid/1.creating-the-app.md Normal file
View File

@@ -0,0 +1,200 @@
## 1: Creating the app
### 1.1: Install Meteor
First, we need to install Meteor by following this [installation guide](https://docs.meteor.com/about/install.html).
### 1.2: Create Meteor Project
The easiest way to setup Meteor with Solid is by using the command `meteor create` with the option `--solid` and your project name:
```shell
meteor create --solid simple-todos-solid
```
Meteor will create all the necessary files for you.
The files located in the `client` directory are setting up your client side (web), you can see for example `client/main.html` where Meteor is rendering your App main component into the HTML.
Also, check the `server` directory where Meteor is setting up the server side (Node.js), you can see the `server/main.js` which would be a good place to initialize your MongoDB database with some data. You don't need to install MongoDB as Meteor provides an embedded version of it ready for you to use.
You can now run your Meteor app using:
```shell
meteor
```
Don't worry, Meteor will keep your app in sync with all your changes from now on.
Take a quick look at all the files created by Meteor, you don't need to understand them now but it's good to know where they are.
Your Solid code will be located inside the `imports/ui` directory, and the `App.jsx` file will be the root component of your Solid To-do app.
### 1.3: Create Tasks
To start working on our todo list app, let’s replace the code of the default starter app with the code below. From there, we’ll talk about what it does.
First, let’s simplify our HTML entry point like so:
::: code-group
```html [client/main.html]
<head>
<title>Simple todo</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
</head>
<body>
<noscript>You need to enable JavaScript to run this app.</noscript>
<div id="root"></div>
</body>
```
:::
The `imports/ui/main.jsx` file should import and render the main Solid component (note: this is referenced via `client/main.js` which imports it):
::: code-group
```jsx [imports/ui/main.jsx]
/* @refresh reload */
import { render } from 'solid-js/web';
import { App } from './App';
import { Meteor } from "meteor/meteor";
import './main.css';
Meteor.startup(() => {
render(() => <App/>, document.getElementById('root'));
});
```
:::
::: code-group
```js [client/main.js]
import '../imports/ui/main';
```
:::
Inside the `imports/ui` folder let us modify `App.jsx` to display a header and a list of tasks:
::: code-group
```jsx [imports/ui/App.jsx]
import { For } from "solid-js";
export const App = () => {
const tasks = [
{ text: 'This is task 1' },
{ text: 'This is task 2' },
{ text: 'This is task 3' },
];
return (
<div class="container">
<header>
<h1>Todo List</h1>
</header>
<ul>
<For each={tasks}>
{(task) => (
<li>{task.text}</li>
)}
</For>
</ul>
</div>
);
};
```
:::
We just modified our main Solid component `App.jsx`, which will be rendered into the `#root` div in the body. It shows a header and a list of tasks. For now, we're using static sample data to display the tasks.
You can now delete these starter files from your project as we don't need them: `Info.jsx`, `Hello.jsx`
### 1.4: View Sample Tasks
As you are not connecting to your server and database yet, we’ve defined some sample data directly in `App.jsx` to render a list of tasks.
At this point meteor should be running on port 3000 so you can visit the running app and see your list with three tasks displayed at [http://localhost:3000/](http://localhost:3000/) - but if meteor is not running, go to your terminal and move to the top directory of your project and type `meteor` then press return to launch the app.
All right! Let’s find out what all these bits of code are doing!
### 1.5: Rendering Data
<img width="688px" src="/tutorials/solid/assets/mermaid-diagram-solid-rendering.png"/>
In Solid with Meteor, your main entry point is `client/main.js`, which imports `imports/ui/main.jsx`
to render your root Solid component `App.jsx` to a target element in the HTML like `<div id="root"></div>` using Solid's `render` function.
Solid components are defined in `.jsx` files using JSX syntax, which can include JavaScript logic, imports, and reactive primitives. The JSX markup can use Solid's control flow components, such as `<For>` for looping and <span v-pre>{expression}</span> for interpolating data.
You can define data and logic directly in the component function. In the code above, we defined a `tasks` array directly in the component. Inside the markup, we use <span v-pre>`<For each={tasks}>`</span> to iterate over the array and display each task's `text`
property using <span v-pre>{task.text}</span>.
For Meteor-specific reactivity (like subscriptions and collections), Solid in Meteor integrates with Meteor's Tracker using hooks like effects or custom trackers. We'll cover that in later steps.
### 1.6: Mobile Look
Let’s see how your app is looking on mobile. You can simulate a mobile environment by `right clicking` your app in the browser (we are assuming you are using Google Chrome, as it is the most popular browser) and then `inspect`, this will open a new window inside your browser called `Dev Tools`. In the `Dev Tools` you have a small icon showing a Mobile device and a Tablet:
<img width="500px" src="/tutorials/solid/assets/step01-dev-tools-mobile-toggle.png"/>
Click on it and then select the phone that you want to simulate and in the top nav bar.
> You can also check your app in your personal cellphone. To do so, connect to your App using your local IP in the navigation browser of your mobile browser.
>
> This command should print your local IP for you on Unix systems
> `ifconfig | grep "inet " | grep -Fv 127.0.0.1 | awk '{print $2}'`
>
> On Microsoft Windows try this in a command prompt
> `ipconfig | findstr "IPv4 Address"`
You should see the following:
<img width="200px" src="/tutorials/solid/assets/step01-mobile-without-meta-tags.png"/>
As you can see, everything is small, as we are not adjusting the view port for mobile devices. You can fix this and other similar issues by adding these lines to your `client/main.html` file, inside the `head` tag, after the `title`.
::: code-group
```html [client/main.html]
<head>
<title>Simple todo</title>
<meta charset="utf-8"/>
<meta http-equiv="x-ua-compatible" content="ie=edge"/>
<meta
name="viewport"
content="width=device-width, height=device-height, viewport-fit=cover, initial-scale=1, maximum-scale=1, minimum-scale=1, user-scalable=no"
/>
<meta name="mobile-web-app-capable" content="yes"/>
<meta name="apple-mobile-web-app-capable" content="yes"/>
</head>
...
```
:::
Now your app should scale properly on mobile devices and look like this:
<img width="200px" src="/tutorials/solid/assets/step01-mobile-with-meta-tags.png"/>
### 1.7: Hot Module Replacement
Meteor uses a package called [hot-module-replacement](https://docs.meteor.com/packages/hot-module-replacement) which is already added for you. This package updates the javascript modules in a running app that were modified during a rebuild. Reduces the feedback cycle while developing, so you can view and test changes quicker (it even updates the app before the build has finished). You are also not going to lose the state, your app code will be updated, and your state will be the same.
By default, when using Solid with Meteor, reactivity is handled by integrating Solid's fine-grained signals and effects with Meteor's Tracker system. This allows real-time updates of the user's screen as data changes in the database without them having to manually refresh. You can achieve this using Tracker.autorun combined with Solid's createEffect or signals for seamless reactivity.
> You can read more about packages [here](https://docs.meteor.com/packages/).
You should also add the package [dev-error-overlay](https://atmospherejs.com/meteor/dev-error-overlay) at this point, so you can see the errors in your web browser.
```shell
meteor add dev-error-overlay
```
You can try to make some mistakes and then you are going to see the errors in the browser and not only in the console.
In the next step we are going to work with our MongoDB database to be able to store our tasks.

183
v3-docs/docs/tutorials/solid/2.collections.md Normal file
View File

@@ -0,0 +1,183 @@
## 2: Collections
Meteor already sets up MongoDB for you. In order to use our database, we need to create a _collection_, which is where we will store our _documents_, in our case our `tasks`.
> You can read more about collections [here](https://v3-docs.meteor.com/api/collections.html).
In this step we will implement all the necessary code to have a basic collection for our tasks up and running.
### 2.1: Create Tasks Collection
We can create a new collection to store our tasks by creating a new file at `imports/api/TasksCollection.js` which instantiates a new Mongo collection and exports it.
::: code-group
```js [imports/api/TasksCollection.js]
import { Mongo } from "meteor/mongo";
export const TasksCollection = new Mongo.Collection("tasks");
```
:::
Notice that we stored the file in the `imports/api` directory, which is a place to store API-related code, like publications and methods. You can name this folder as you want, this is just a choice.
If there is a `imports/api/links.js` file from the starter project, you can delete that now as we don't need it.
> You can read more about app structure and imports/exports [here](http://guide.meteor.com/structure.html).
### 2.2: Initialize Tasks Collection
For our collection to work, you need to import it in the server so it sets some plumbing up.
You can either use `import "/imports/api/TasksCollection"` or `import { TasksCollection } from "/imports/api/TasksCollection"` if you are going to use on the same file, but make sure it is imported.
Now it is easy to check if there is data or not in our collection, otherwise, we can insert some sample data easily as well.
You don't need to keep the old content of `server/main.js`.
::: code-group
```js [server/main.js]
import { Meteor } from "meteor/meteor";
import { TasksCollection } from "/imports/api/TasksCollection";
const insertTask = async (taskText) =>
await TasksCollection.insertAsync({ text: taskText });
Meteor.startup(async () => {
if (await TasksCollection.find().countAsync() === 0) {
[
"First Task",
"Second Task",
"Third Task",
"Fourth Task",
"Fifth Task",
"Sixth Task",
"Seventh Task",
].forEach(insertTask);
}
});
```
:::
So you are importing the `TasksCollection` and adding a few tasks to it iterating over an array of strings and for each string calling a function to insert this string as our `text` field in our `task` document.
### 2.3: Render Tasks Collection
Now comes the fun part, you will render the tasks with Solid. That will be pretty simple.
In your `App.jsx` file, import the `TasksCollection` and use Tracker to subscribe and fetch the tasks reactively:
::: code-group
```jsx [imports/ui/App.jsx]
import { createSignal, For, Show } from "solid-js";
import { Meteor } from "meteor/meteor";
import { Tracker } from "meteor/tracker";
import { TasksCollection } from "../api/TasksCollection";
export const App = () => {
const subscription = Meteor.subscribe("tasks");
const [isReady, setIsReady] = createSignal(subscription.ready());
const [tasks, setTasks] = createSignal([]);
Tracker.autorun(async () => {
setIsReady(subscription.ready());
setTasks(await TasksCollection.find().fetchAsync());
});
return (
<div class="container">
<header>
<h1>Todo List</h1>
</header>
<Show
when={isReady()}
fallback={<div>Loading ...</div>}
>
<ul>
<For each={tasks()}>
{(task) => (
<li>{task.text}</li>
)}
</For>
</ul>
</Show>
</div>
);
};
```
:::
But wait! Something is missing. If you run your app now, you'll see that you don't render any tasks.
That's because we need to publish our data to the client.
> For more information on Publications/Subscriptions, please check our [docs](https://v3-docs.meteor.com/api/meteor.html#pubsub).
Meteor doesn't need REST calls. It instead relies on synchronizing the MongoDB on the server with a MiniMongoDB on the client. It does this by first publishing collections on the server and then subscribing to them on the client.
First, create a publication for our tasks:
::: code-group
```javascript [imports/api/TasksPublications.js]
import { Meteor } from "meteor/meteor";
import { TasksCollection } from "./TasksCollection";
Meteor.publish("tasks", function () {
return TasksCollection.find();
});
```
:::
Now, we need to import this file in our server:
::: code-group
```js [server/main.js]
...
import { TasksCollection } from '/imports/api/TasksCollection';
import "../imports/api/TasksPublications"; // [!code highlight]
const insertTask = taskText => TasksCollection.insertAsync({ text: taskText });
...
```
:::
The only thing left is subscribe to this publication, which we've already added in `App.jsx` using:
::: code-group
```jsx [imports/ui/App.jsx]
...
const subscription = Meteor.subscribe("tasks");
...
```
:::
See how your app should look like now:
<img width="200px" src="/tutorials/solid/assets/collections-tasks-list.png"/>
You can change your data on MongoDB in the server and your app will react and re-render for you.
You can connect to your MongoDB running `meteor mongo` in the terminal from your app folder or using a Mongo UI client, like [NoSQLBooster](https://nosqlbooster.com/downloads). Your embedded MongoDB is running in port `3001`.
See how to connect:
<img width="500px" src="/tutorials/solid/assets/collections-connect-db.png"/>
See your database:
<img width="500px" src="/tutorials/solid/assets/collections-see-database.png"/>
You can double-click your collection to see the documents stored on it:
<img width="500px" src="/tutorials/solid/assets/collections-documents.png"/>
In the next step, we are going to create tasks using a form.

248
v3-docs/docs/tutorials/solid/3.forms-and-events.md Normal file
View File

@@ -0,0 +1,248 @@
## 3: Forms and Events
All apps need to allow the user to perform some sort of interaction with the data that is stored. In our case, the first type of interaction is to insert new tasks. Without it, our To-Do app wouldn't be very helpful.
One of the main ways in which a user can insert or edit data on a website is through forms. In most cases, it is a good idea to use the `<form>` tag since it gives semantic meaning to the elements inside it.
### 3.1: Create Task Form
Create a new `form` inside the `App.jsx` file, and inside we’ll add an input field and a button. Place it between the `header` and the `Show` elements:
::: code-group
```jsx [imports/ui/App.jsx]
...
</header>
<form class="task-form" onSubmit={addTask}>
<input
type="text"
placeholder="Type to add new tasks"
value={newTask()}
onInput={(e) => setNewTask(e.currentTarget.value)}
/>
<button type="submit">Add Task</button>
</form>
<Show
...
```
:::
In the code above, we've integrated the form directly into the `App.jsx` component, positioning it above the task list. We're using Solid's signals for two-way binding on the input (via `value` and `onInput`) and an `onSubmit` handler for form submission.
Let's now add our signals and `addTask()` function handler inside the top of the `App` function definition. It will call a Meteor method `tasks.insert` that isn't yet created but we'll soon make:
::: code-group
```jsx [imports/ui/App.jsx]
...
export const App = () => {
const [newTask, setNewTask] = createSignal('');
const addTask = async (event) => {
event.preventDefault();
if (newTask().trim()) {
await Meteor.callAsync("tasks.insert", {
text: newTask(),
createdAt: new Date(),
});
setNewTask('');
}
};
const subscription = Meteor.subscribe("tasks");
...
```
:::
Altogether, our file should look like:
::: code-group
```jsx [imports/ui/App.jsx]
import { createSignal, For, Show } from "solid-js";
import { Meteor } from "meteor/meteor";
import { Tracker } from "meteor/tracker";
import { TasksCollection } from "../api/TasksCollection";
export const App = () => {
const [newTask, setNewTask] = createSignal('');
const addTask = async (event) => {
event.preventDefault();
if (newTask().trim()) {
await Meteor.callAsync("tasks.insert", {
text: newTask(),
createdAt: new Date(),
});
setNewTask('');
}
};
const subscription = Meteor.subscribe("tasks");
const [isReady, setIsReady] = createSignal(subscription.ready());
const [tasks, setTasks] = createSignal([]);
Tracker.autorun(async () => {
setIsReady(subscription.ready());
setTasks(await TasksCollection.find().fetchAsync());
});
return (
<div class="container">
<header>
<h1>Todo List</h1>
</header>
<form class="task-form" onSubmit={addTask}>
<input
type="text"
placeholder="Type to add new tasks"
value={newTask()}
onInput={(e) => setNewTask(e.currentTarget.value)}
/>
<button type="submit">Add Task</button>
</form>
<Show
when={isReady()}
fallback={<div>Loading ...</div>}
>
<ul>
<For each={tasks()}>
{(task) => (
<li>{task.text}</li>
)}
</For>
</ul>
</Show>
</div>
);
};
```
:::
### 3.2: Update the Stylesheet
You also can style it as you wish. For now, we only need some margin at the top so the form doesn't seem off the mark. Add the CSS class `.task-form`, this needs to be the same name in your `class` attribute in the form element. Notice how in Solid you don't use `className` like you would in React.
::: code-group
```css [imports/ui/main.css]
...
.task-form {
margin-top: 1rem;
}
...
```
:::
### 3.3: Add Submit Handler
Now let's create a function to handle the form submit and insert a new task into the database. To do it, we will need to implement a Meteor Method.
Methods are essentially RPC calls to the server that let you perform operations on the server side securely. You can read more about Meteor Methods [here](https://guide.meteor.com/methods.html).
To create your methods, you can create a file called `TasksMethods.js`.
::: code-group
```javascript [imports/api/TasksMethods.js]
import { Meteor } from "meteor/meteor";
import { TasksCollection } from "./TasksCollection";
Meteor.methods({
"tasks.insert"(doc) {
return TasksCollection.insertAsync(doc);
},
});
```
:::
Remember to import your method on the `main.js` server file, delete the `insertTask` function, and invoke the new meteor method inside the `forEach` block.
::: code-group
```javascript [server/main.js]
import { Meteor } from "meteor/meteor";
import { TasksCollection } from "/imports/api/TasksCollection";
import "../imports/api/TasksPublications";
import "../imports/api/TasksMethods"; // [!code highlight]
Meteor.startup(async () => {
if ((await TasksCollection.find().countAsync()) === 0) {
[
"First Task",
"Second Task",
"Third Task",
"Fourth Task",
"Fifth Task",
"Sixth Task",
"Seventh Task",
].forEach((taskName) => {
Meteor.callAsync("tasks.insert", { // [!code highlight]
text: taskName, // [!code highlight]
createdAt: new Date(), // [!code highlight]
});
});
}
});
```
:::
Inside the `forEach` function, we are adding a task to the `tasks` collection by calling `Meteor.callAsync()`. The first argument is the name of the method we want to call, and the second argument is the text of the task.
Also, insert a date `createdAt` in your `task` document so you know when each task was created.
Now we need to import `TasksMethods.js` in a client-side file to enable optimistic UI (e.g., in `imports/ui/main.jsx`):
::: code-group
```jsx [imports/ui/main.jsx]
/* @refresh reload */
import { render } from 'solid-js/web';
import { App } from './App';
import { Meteor } from "meteor/meteor";
import './main.css';
import "/imports/api/TasksMethods"; // [!code highlight] // this import allows for optimistic execution
Meteor.startup(() => {
render(() => <App/>, document.getElementById('root'));
});
```
:::
In the `addTask` function (shown in 3.1), we prevent the default form submission, get the input value, call the Meteor method to insert the task optimistically, and clear the input.
Meteor methods execute optimistically on the client using MiniMongo while simultaneously calling the server. If the server call fails, MiniMongo rolls back the change, providing a speedy user experience. It's a bit like [rollback netcode](https://glossary.infil.net/?t=Rollback%20Netcode) in fighting video games.
### 3.4: Show Newest Tasks First
Now you just need to make a change that will make users happy: we need to show the newest tasks first. We can accomplish this quite quickly by sorting our [Mongo](https://guide.meteor.com/collections.html#mongo-collections) query.
::: code-group
```jsx [imports/ui/App.jsx]
...
Tracker.autorun(async () => {
setIsReady(subscription.ready());
setTasks(await TasksCollection.find({}, { sort: { createdAt: -1 } }).fetchAsync()); // [!code highlight]
});
...
```
:::
Your app should look like this:
<img width="200px" src="/tutorials/solid/assets/step03-form-new-task.png"/>
<img width="200px" src="/tutorials/solid/assets/step03-new-task-on-list.png"/>
In the next step, we are going to update your tasks state and provide a way for users to remove tasks.

216
v3-docs/docs/tutorials/solid/4.update-and-remove.md Normal file
View File

@@ -0,0 +1,216 @@
## 4: Update and Remove
Up until now, you have only inserted documents into our collection. Let's take a look at how you can update and remove them by interacting with the user interface.
### 4.1: Add Checkbox
First, you need to add a `checkbox` element to your `Task` component.
Next, let’s create a new file for our `task` in `imports/ui/Task.jsx`, so we can start to separate the logic in our app.
::: code-group
```jsx [imports/ui/Task.jsx]
import { Meteor } from "meteor/meteor";
export const Task = (props) => {
const { task } = props;
const toggleChecked = async () => {
await Meteor.callAsync("tasks.toggleChecked", { _id: task._id, isChecked: task.isChecked });
};
return (
<li>
<label>
<input type="checkbox" checked={task.isChecked} onChange={toggleChecked} />
<span>{task.text}</span>
</label>
</li>
);
};
```
:::
Now, update `App.jsx` to import and use the `Task` component in the `<For>` loop. Remove the old `<li>` markup.
::: code-group
```jsx [imports/ui/App.jsx]
import { createSignal, For, Show } from "solid-js";
import { Meteor } from "meteor/meteor";
import { Tracker } from "meteor/tracker";
import { TasksCollection } from "../api/TasksCollection";
import { Task } from "./Task.jsx"; // [!code highlight]
export const App = () => {
const [newTask, setNewTask] = createSignal('');
const addTask = async (event) => {
event.preventDefault();
if (newTask().trim()) {
await Meteor.callAsync("tasks.insert", {
text: newTask(),
createdAt: new Date(),
});
setNewTask('');
}
};
const subscription = Meteor.subscribe("tasks");
const [isReady, setIsReady] = createSignal(subscription.ready());
const [tasks, setTasks] = createSignal([]);
Tracker.autorun(async () => {
setIsReady(subscription.ready());
setTasks(await TasksCollection.find({}, { sort: { createdAt: -1 } }).fetchAsync());
});
return (
<div class="container">
<header>
<h1>Todo List</h1>
</header>
<form class="task-form" onSubmit={addTask}>
<input
type="text"
placeholder="Type to add new tasks"
value={newTask()}
onInput={(e) => setNewTask(e.currentTarget.value)}
/>
<button type="submit">Add Task</button>
</form>
<Show
when={isReady()}
fallback={<div>Loading ...</div>}
>
<ul>
<For each={tasks()}>
{(task) => (
<Task task={task} /> // [!code highlight]
)}
</For>
</ul>
</Show>
</div>
);
};
```
:::
### 4.2: Toggle Checkbox
Now you can update your task document by toggling its `isChecked` field.
First, create a new method called `tasks.toggleChecked` to update the `isChecked` property.
::: code-group
```js [imports/api/TasksMethods.js]
import { Meteor } from "meteor/meteor";
import { TasksCollection } from "./TasksCollection";
Meteor.methods({
...
"tasks.toggleChecked"({ _id, isChecked }) {
return TasksCollection.updateAsync(_id, {
$set: { isChecked: !isChecked },
});
},
});
```
:::
In `Task.jsx` (as shown above), we've added an `onChange` handler that calls the method to toggle the checked state.
Toggling checkboxes should now persist in the DB even if you refresh the web browser.
Your app should look like this:
<img width="200px" src="/tutorials/solid/assets/step04-checkbox.png"/>
If your computer is fast enough, it's possible that when it sets up the default tasks a few will have the same date. That will cause them to non-deterministically "jump around" in the UI as you toggle checkboxes and the UI reactively updates. To make it stable, you can add a secondary sort on the `_id` of the task:
::: code-group
```jsx [imports/ui/App.jsx]
...
Tracker.autorun(async () => {
setIsReady(subscription.ready());
setTasks(await TasksCollection.find({}, { sort: { createdAt: -1, _id: -1 } }).fetchAsync()); // [!code highlight]
});
...
```
:::
### 4.3: Remove tasks
You can remove tasks with just a few lines of code.
First, add a button after the `label` in your `Task` component and a `deleteTask` function.
::: code-group
```jsx [imports/ui/Task.jsx]
import { Meteor } from "meteor/meteor";
export const Task = (props) => {
const { task } = props;
const toggleChecked = async () => {
await Meteor.callAsync("tasks.toggleChecked", { _id: task._id, isChecked: task.isChecked });
};
const deleteTask = async () => { // [!code highlight]
await Meteor.callAsync("tasks.delete", { _id: task._id }); // [!code highlight]
}; // [!code highlight]
return (
<li>
<label>
<input type="checkbox" checked={task.isChecked} onChange={toggleChecked} />
<span>{task.text}</span>
</label>
<button class="delete" onClick={deleteTask}>&times;</button> // [!code highlight]
</li>
);
};
```
:::
Next you need to have a function to delete the task. For that, let's create a new method called `tasks.delete`:
::: code-group
```js [imports/api/TasksMethods.js]
import { Meteor } from "meteor/meteor";
import { TasksCollection } from "./TasksCollection";
Meteor.methods({
...
"tasks.delete"({ _id }) {
return TasksCollection.removeAsync(_id);
},
});
```
:::
Now the removal logic is handled in `Task.jsx` via the `onClick` event on the delete button, which calls the Meteor method.
Your app should look like this:
<img width="200px" src="/tutorials/solid/assets/step04-delete-button.png"/>
### 4.4: Getting data in event handlers
In a collection, every inserted document has a unique `_id` field that can refer to that specific document. Inside the component, the `task` prop provides access to the task object, including its `_id`
and other fields like `isChecked` and `text`. We use these to call Meteor methods for updating or removing the specific task.
In the next step, we are going to improve the look of your app using CSS with Flexbox.

231
v3-docs/docs/tutorials/solid/5.styles.md Normal file
View File

@@ -0,0 +1,231 @@
## 5: Styles
### 5.1: CSS
Our user interface up until this point has looked quite ugly. Let's add some basic styling which will serve as the foundation for a more professional looking app.
Replace the content of our `imports/ui/main.css` file with the one below, the idea is to have an app bar at the top, and a scrollable content including:
- form to add new tasks;
- list of tasks.
::: code-group
```css [imports/ui/main.css]
body {
font-family: sans-serif;
background-color: #315481;
background-image: linear-gradient(to bottom, #315481, #918e82 100%);
background-attachment: fixed;
position: absolute;
top: 0;
bottom: 0;
left: 0;
right: 0;
padding: 0;
margin: 0;
font-size: 14px;
}
button {
font-weight: bold;
font-size: 1em;
border: none;
color: white;
box-shadow: 0 3px 3px rgba(34, 25, 25, 0.4);
padding: 5px;
cursor: pointer;
}
button:focus {
outline: 0;
}
.app {
display: flex;
flex-direction: column;
height: 100vh;
}
.app-header {
flex-grow: 1;
white-space: nowrap;
overflow: hidden;
text-overflow: ellipsis;
}
.main {
display: flex;
flex-direction: column;
flex-grow: 1;
overflow: auto;
background: white;
}
.main::-webkit-scrollbar {
width: 0;
height: 0;
background: inherit;
}
header {
background: #d2edf4;
background-image: linear-gradient(to bottom, #d0edf5, #e1e5f0 100%);
padding: 20px 15px 15px 15px;
position: relative;
box-shadow: 0 3px 3px rgba(34, 25, 25, 0.4);
}
.app-bar {
display: flex;
justify-content: space-between;
}
.app-bar h1 {
font-size: 1.5em;
margin: 0;
display: inline-block;
margin-right: 1em;
}
.task-form {
display: flex;
margin: 16px;
}
.task-form > input {
flex-grow: 1;
box-sizing: border-box;
padding: 10px 6px;
background: transparent;
border: 1px solid #aaa;
width: 100%;
font-size: 1em;
margin-right: 16px;
}
.task-form > input:focus {
outline: 0;
}
.task-form > button {
min-width: 100px;
height: 95%;
background-color: #315481;
}
.tasks {
list-style-type: none;
padding-inline-start: 0;
padding-left: 16px;
padding-right: 16px;
margin-block-start: 0;
margin-block-end: 0;
}
.tasks > li {
display: flex;
padding: 16px;
border-bottom: #eee solid 1px;
align-items: center;
}
.tasks > li > label {
flex-grow: 1;
}
.tasks > li > button {
justify-self: flex-end;
background-color: #ff3046;
}
```
:::
> If you want to learn more about this stylesheet check this article about [Flexbox](https://css-tricks.com/snippets/css/a-guide-to-flexbox/), and also this free [video tutorial](https://flexbox.io/) about it from [Wes Bos](https://twitter.com/wesbos).
>
> Flexbox is an excellent tool to distribute and align elements in your UI.
### 5.2: Applying styles
Now you need to add some elements around your components. You are going to add a `class` to your main `div` in the `App.jsx`, also a `header` element with a few `div` elements around your `h1`, and a main `div` around your form and list. Check below how it should be; pay attention to the name of the classes, they need to be the same as in the CSS file:
::: code-group
```jsx [imports/ui/App.jsx]
import { createSignal, For, Show } from "solid-js";
import { Meteor } from "meteor/meteor";
import { Tracker } from "meteor/tracker";
import { TasksCollection } from "../api/TasksCollection";
import { Task } from "./Task.jsx";
export const App = () => {
const [newTask, setNewTask] = createSignal('');
const addTask = async (event) => {
event.preventDefault();
if (newTask().trim()) {
await Meteor.callAsync("tasks.insert", {
text: newTask(),
createdAt: new Date(),
});
setNewTask('');
}
};
const subscription = Meteor.subscribe("tasks");
const [isReady, setIsReady] = createSignal(subscription.ready());
const [tasks, setTasks] = createSignal([]);
Tracker.autorun(async () => {
setIsReady(subscription.ready());
setTasks(await TasksCollection.find({}, { sort: { createdAt: -1, _id: -1 } }).fetchAsync());
});
return (
<div class="app">
<header>
<div class="app-bar">
<div class="app-header">
<h1>📝️ Todo List</h1>
</div>
</div>
</header>
<div class="main">
<form class="task-form" onSubmit={addTask}>
<input
type="text"
placeholder="Type to add new tasks"
value={newTask()}
onInput={(e) => setNewTask(e.currentTarget.value)}
/>
<button type="submit">Add Task</button>
</form>
<Show
when={isReady()}
fallback={<div>Loading ...</div>}
>
<ul class="tasks">
<For each={tasks()}>
{(task) => (
<Task task={task} />
)}
</For>
</ul>
</Show>
</div>
</div>
);
};
```
:::
Your app should look like this:
<img width="200px" src="/tutorials/solid/assets/step05-styles.png"/>
In the next step, we are going to make this task list more interactive, for example, providing a way to filter tasks.

322
v3-docs/docs/tutorials/solid/6.filter-tasks.md Normal file
View File

@@ -0,0 +1,322 @@
## 6: Filter tasks
In this step, you will filter your tasks by status and show the number of pending tasks.
### 6.1: Reactive State
First, you will add a button to show or hide the completed tasks from the list.
In Solid, we manage component state using signals for reactivity. Solid's fine-grained reactivity will automatically update the UI when the state changes.
We'll add a `hideCompleted` variable to the `App.jsx` component and a function to toggle it.
::: code-group
```jsx [imports/ui/App.jsx]
import { createSignal, For, Show } from "solid-js";
import { Meteor } from "meteor/meteor";
import { Tracker } from "meteor/tracker";
import { TasksCollection } from "../api/TasksCollection";
import { Task } from "./Task.jsx";
export const App = () => {
const [newTask, setNewTask] = createSignal('');
const [hideCompleted, setHideCompleted] = createSignal(false); // [!code highlight]
const addTask = async (event) => {
event.preventDefault();
if (newTask().trim()) {
await Meteor.callAsync("tasks.insert", {
text: newTask(),
createdAt: new Date(),
});
setNewTask('');
}
};
const toggleHideCompleted = () => { // [!code highlight]
setHideCompleted(!hideCompleted()); // [!code highlight]
}; // [!code highlight]
const subscription = Meteor.subscribe("tasks");
const [isReady, setIsReady] = createSignal(subscription.ready());
const [tasks, setTasks] = createSignal([]);
Tracker.autorun(async () => {
setIsReady(subscription.ready());
setTasks(await TasksCollection.find({}, { sort: { createdAt: -1, _id: -1 } }).fetchAsync());
});
// markup will be updated in next steps
};
```
:::
Then, add the button in the markup to toggle the state:
::: code-group
```jsx [imports/ui/App.jsx]
// ... javascript above remains the same
return (
<div class="app">
<header>
<div class="app-bar">
<div class="app-header">
<h1>📝️ Todo List</h1>
</div>
</div>
</header>
<div class="main">
<form class="task-form" onSubmit={addTask}>
<input
type="text"
placeholder="Type to add new tasks"
value={newTask()}
onInput={(e) => setNewTask(e.currentTarget.value)}
/>
<button type="submit">Add Task</button>
</form>
<div class="filter"> // [!code highlight]
<button onClick={toggleHideCompleted}> // [!code highlight]
<Show // [!code highlight]
when={hideCompleted()} // [!code highlight]
fallback="Hide Completed" // [!code highlight]
> // [!code highlight]
Show All // [!code highlight]
</Show> // [!code highlight]
</button> // [!code highlight]
</div> // [!code highlight]
<Show
when={isReady()}
fallback={<div>Loading ...</div>}
>
<ul class="tasks">
<For each={tasks()}>
{(task) => (
<Task task={task} />
)}
</For>
</ul>
</Show>
</div>
</div>
);
```
:::
You may notice we’re using `<Show>` for the button text. You can learn more about Solid's conditional rendering [here](https://docs.solidjs.com/reference/components/show).
### 6.2: Button style
You should add some style to your button so it does not look gray and without a good contrast. You can use the styles below as a reference:
::: code-group
```css [imports/ui/main.css]
.filter {
display: flex;
justify-content: center;
}
.filter > button {
background-color: #62807e;
}
```
:::
### 6.3: Filter Tasks
Now, update the reactive tasks fetch to apply the filter if `hideCompleted` is true. We'll also add a reactive signal for the incomplete count using another Tracker.autorun.
::: code-group
```jsx [imports/ui/App.jsx]
import { createSignal, For, Show } from "solid-js";
import { Meteor } from "meteor/meteor";
import { Tracker } from "meteor/tracker";
import { TasksCollection } from "../api/TasksCollection";
import { Task } from "./Task.jsx";
export const App = () => {
const [newTask, setNewTask] = createSignal('');
const [hideCompleted, setHideCompleted] = createSignal(false);
const addTask = async (event) => {
event.preventDefault();
if (newTask().trim()) {
await Meteor.callAsync("tasks.insert", {
text: newTask(),
createdAt: new Date(),
});
setNewTask('');
}
};
const toggleHideCompleted = () => {
setHideCompleted(!hideCompleted());
};
const subscription = Meteor.subscribe("tasks");
const [isReady, setIsReady] = createSignal(subscription.ready());
const [tasks, setTasks] = createSignal([]);
Tracker.autorun(async () => {
setIsReady(subscription.ready());
const query = hideCompleted() ? { isChecked: { $ne: true } } : {}; // [!code highlight]
setTasks(await TasksCollection.find(query, { sort: { createdAt: -1, _id: -1 } }).fetchAsync()); // [!code highlight]
});
// Reactive incomplete count // [!code highlight]
const [incompleteCount, setIncompleteCount] = createSignal(0); // [!code highlight]
Tracker.autorun(async () => { // [!code highlight]
setIncompleteCount(await TasksCollection.find({ isChecked: { $ne: true } }).countAsync()); // [!code highlight]
}); // [!code highlight]
// markup remains the same
};
```
:::
### 6.4: Meteor Dev Tools Extension
You can install an extension to visualize the data in your Mini Mongo.
[Meteor DevTools Evolved](https://chrome.google.com/webstore/detail/meteor-devtools-evolved/ibniinmoafhgbifjojidlagmggecmpgf) will help you to debug your app as you can see what data is on Mini Mongo.
<img width="800px" src="/tutorials/solid/assets/step06-extension.png"/>
You can also see all the messages that Meteor is sending and receiving from the server, this is useful for you to learn more about how Meteor works.
<img width="800px" src="/tutorials/solid/assets/step06-ddp-messages.png"/>
Install it in your Google Chrome browser using this [link](https://chrome.google.com/webstore/detail/meteor-devtools-evolved/ibniinmoafhgbifjojidlagmggecmpgf).
### 6.5: Pending tasks
Update the App component in order to show the number of pending tasks in the app bar.
You should avoid adding zero to your app bar when there are no pending tasks. Use the reactive `incompleteCount` in the header:
::: code-group
```jsx [imports/ui/App.jsx]
// ... javascript with incompleteCount remains the same
return (
<div class="app">
<header>
<div class="app-bar">
<div class="app-header">
<h1>📝️ To Do List {incompleteCount() > 0 ? `(${incompleteCount()})` : ''}</h1> // [!code highlight]
</div>
</div>
</header>
// rest of markup
</div>
);
```
:::
### 6.6: Make the Hide/Show toggle work
If you try the Hide/Show completed toggle button you'll see that the text changes but it doesn't actually do anything to the list of tasks. The toggle button isn't triggering the expected filtering because the `hideCompleted` signal (from Solid) isn't integrated with Meteor's Tracker reactivity system. Tracker.autorun only re-runs when its internal dependencies (like subscription data or ReactiveVars) change—not when Solid signals change. So, updating `hideCompleted` via `setHideCompleted` changes the button text (via Solid's `<Show>`), but it doesn't re-execute the autorun to update the query and re-fetch tasks.
This is a common challenge when bridging Solid's fine-grained reactivity with Meteor's Tracker. I'll explain the fix below with minimal changes to your code.
To make Tracker react to changes in `hideCompleted`, we'll use Meteor's `ReactiveVar`
to hold the filter state. This makes the value reactive within Tracker, so the autorun re-runs automatically when it changes. We'll sync it with your Solid signal for the UI.
Add this import at the top of `App.jsx`
::: code-group
```jsx [imports/ui/App.jsx]
import { ReactiveVar } from 'meteor/reactive-var';
```
:::
Initialize a ReactiveVar and use a Solid `createEffect` to keep it in sync with your `hideCompleted` signal. Update your `App` component like this:
Add this import at the top of `App.jsx`
::: code-group
```jsx [imports/ui/App.jsx]
...
import { createSignal, For, Show, createEffect } from "solid-js"; // Updated import
...
export const App = () => {
const [newTask, setNewTask] = createSignal('');
const [hideCompleted, setHideCompleted] = createSignal(false);
// New: ReactiveVar for Tracker integration
const hideCompletedVar = new ReactiveVar(false); // [!code highlight]
// New: Sync Solid signal to ReactiveVar (triggers Tracker re-run) // [!code highlight]
createEffect(() => { // [!code highlight]
hideCompletedVar.set(hideCompleted()); // [!code highlight]
}); // [!code highlight]
const addTask = async (event) => {
event.preventDefault();
if (newTask().trim()) {
await Meteor.callAsync("tasks.insert", {
text: newTask(),
createdAt: new Date(),
});
setNewTask('');
}
};
const toggleHideCompleted = () => {
setHideCompleted(!hideCompleted());
};
const subscription = Meteor.subscribe("tasks");
const [isReady, setIsReady] = createSignal(subscription.ready());
const [tasks, setTasks] = createSignal([]);
Tracker.autorun(async () => {
setIsReady(subscription.ready());
// Use ReactiveVar in the query for Tracker reactivity // [!code highlight]
const query = hideCompletedVar.get() ? { isChecked: { $ne: true } } : {}; // [!code highlight]
setTasks(await TasksCollection.find(query, { sort: { createdAt: -1, _id: -1 } }).fetchAsync());
});
// Reactive incomplete count (unchanged)
const [incompleteCount, setIncompleteCount] = createSignal(0);
Tracker.autorun(async () => {
setIncompleteCount(await TasksCollection.find({ isChecked: { $ne: true } }).countAsync());
});
// Return statement remains the same
return (
// ... your JSX here, unchanged
);
};
```
:::
Why this works:
1. `ReactiveVar` bridges the systems: When you toggle `hideCompleted` (Solid signal), the `createEffect` updates the `ReactiveVar`. This invalidates and re-runs the Tracker.autorun, which re-fetches tasks with the updated query.
2. No major rewrites: Your existing signals and UI logic stay intact.
3. Performance: Tracker handles the re-fetch efficiently, and Solid updates the UI via the `tasks` signal.
Your app should look like this:
<img width="200px" src="/tutorials/solid/assets/step06-all.png"/>
<img width="200px" src="/tutorials/solid/assets/step06-filtered.png"/>
In the next step we are going to include user access in your app.

414
v3-docs/docs/tutorials/solid/7.adding-user-accounts.md Normal file
View File

@@ -0,0 +1,414 @@
## 7: Adding User Accounts
### 7.1: Password Authentication
Meteor already comes with a basic authentication and account management system out of the box, so you only need to add the `accounts-password` to enable username and password authentication:
```shell
meteor add accounts-password
```
> There are many more authentication methods supported. You can read more about the accounts system [here](https://v3-docs.meteor.com/api/accounts.html).
We also recommend you to install `bcrypt` node module, otherwise, you are going to see a warning saying that you are using a pure-Javascript implementation of it.
```shell
meteor npm install --save bcrypt
```
> You should always use `meteor npm` instead of only `npm` so you always use the `npm` version pinned by Meteor, this helps you to avoid problems due to different versions of npm installing different modules.
### 7.2: Create User Account
Now you can create a default user for our app, we are going to use `meteorite` as username, we just create a new user on server startup if we didn't find it in the database.
::: code-group
```js [server/main.js]
import { Meteor } from 'meteor/meteor';
import { Accounts } from 'meteor/accounts-base'; // [!code highlight]
import { TasksCollection } from '/imports/api/TasksCollection';
import "../imports/api/TasksPublications";
import "../imports/api/TasksMethods";
const SEED_USERNAME = 'meteorite'; // [!code highlight]
const SEED_PASSWORD = 'password'; // [!code highlight]
Meteor.startup(async () => {
if (!(await Accounts.findUserByUsername(SEED_USERNAME))) { // [!code highlight]
await Accounts.createUser({ // [!code highlight]
username: SEED_USERNAME, // [!code highlight]
password: SEED_PASSWORD, // [!code highlight]
}); // [!code highlight]
} // [!code highlight]
...
});
```
:::
You should not see anything different in your app UI yet.
### 7.3: Login Form
You need to provide a way for the users to input the credentials and authenticate, for that we need a form.
Our login form will be simple, with just two fields (username and password) and a button. You should use `Meteor.loginWithPassword(username, password)`; to authenticate your user with the provided inputs.
Create a new component `Login.jsx` in `imports/ui/`:
::: code-group
```jsx [imports/ui/Login.jsx]
import { createSignal } from "solid-js";
import { Meteor } from "meteor/meteor";
export const Login = () => {
const [username, setUsername] = createSignal('');
const [password, setPassword] = createSignal('');
const login = async (event) => {
event.preventDefault();
await Meteor.loginWithPassword(username(), password());
};
return (
<form class="login-form" onSubmit={login}>
<div>
<label for="username">Username</label>
<input
type="text"
placeholder="Username"
name="username"
required
value={username()}
onInput={(e) => setUsername(e.currentTarget.value)}
/>
</div>
<div>
<label for="password">Password</label>
<input
type="password"
placeholder="Password"
name="password"
required
value={password()}
onInput={(e) => setPassword(e.currentTarget.value)}
/>
</div>
<div>
<button type="submit">Log In</button>
</div>
</form>
);
};
```
:::
Be sure also to import the login form in `App.jsx`.
::: code-group
```jsx [imports/ui/App.jsx]
import { ReactiveVar } from 'meteor/reactive-var';
import { createSignal, For, Show, createEffect } from "solid-js";
import { Meteor } from "meteor/meteor";
import { Tracker } from "meteor/tracker";
import { TasksCollection } from "../api/TasksCollection";
import { Task } from "./Task.jsx";
import { Login } from "./Login.jsx"; // [!code highlight]
// ... rest of the script
```
:::
Ok, now you have a form, let's use it.
### 7.4: Require Authentication
Our app should only allow an authenticated user to access its task management features.
We can accomplish that by rendering the `Login` component when we don’t have an authenticated user. Otherwise, we render the form, filter, and list.
To achieve this, we will use a conditional `<Show>` in `App.jsx`:
::: code-group
```jsx [imports/ui/App.jsx]
// ... other imports and code
const [currentUser, setCurrentUser] = createSignal(Meteor.user()); // Reactive current user // [!code highlight]
Tracker.autorun(() => { // [!code highlight]
setCurrentUser(Meteor.user()); // [!code highlight]
}); // [!code highlight]
// ... rest of script
return (
<div class="app">
<header>
<div class="app-bar">
<div class="app-header">
<h1>📝️ To Do List {incompleteCount() > 0 ? `(${incompleteCount()})` : ''}</h1>
</div>
</div>
</header>
<div class="main">
<Show // [!code highlight]
when={currentUser()} // [!code highlight]
fallback={<Login />} // [!code highlight]
> // [!code highlight]
<form class="task-form" onSubmit={addTask}>
<input
type="text"
placeholder="Type to add new tasks"
value={newTask()}
onInput={(e) => setNewTask(e.currentTarget.value)}
/>
<button type="submit">Add Task</button>
</form>
<div class="filter">
<button onClick={toggleHideCompleted}>
<Show
when={hideCompleted()}
fallback="Hide Completed"
>
Show All
</Show>
</button>
</div>
<Show
when={isReady()}
fallback={<div>Loading ...</div>}
>
<ul class="tasks">
<For each={tasks()}>
{(task) => (
<Task task={task} />
)}
</For>
</ul>
</Show>
</Show> // [!code highlight]
</div>
</div>
);
```
:::
As you can see, if the user is logged in, we render the whole app (`currentUser` is truthy). Otherwise, we render the Login component.
### 7.5: Login Form style
Ok, let's style the login form now:
::: code-group
```css [imports/ui/main.css]
.login-form {
display: flex;
flex-direction: column;
height: 100%;
justify-content: center;
align-items: center;
}
.login-form > div {
margin: 8px;
}
.login-form > div > label {
font-weight: bold;
}
.login-form > div > input {
flex-grow: 1;
box-sizing: border-box;
padding: 10px 6px;
background: transparent;
border: 1px solid #aaa;
width: 100%;
font-size: 1em;
margin-right: 16px;
margin-top: 4px;
}
.login-form > div > input:focus {
outline: 0;
}
.login-form > div > button {
background-color: #62807e;
}
```
:::
Now your login form should be centralized and beautiful.
### 7.6: Server startup
Every task should have an owner from now on. So go to your database, as you learned before, and remove all the tasks from there:
`db.tasks.remove({});`
Change your `server/main.js` to add the seed tasks using your `meteorite` user as owner.
Make sure you restart the server after this change so `Meteor.startup` block will run again. This is probably going to happen automatically anyway as you are going to make changes in the server side code.
::: code-group
```js [server/main.js]
...
const user = await Accounts.findUserByUsername(SEED_USERNAME);
if ((await TasksCollection.find().countAsync()) === 0) {
[
"First Task",
"Second Task",
"Third Task",
"Fourth Task",
"Fifth Task",
"Sixth Task",
"Seventh Task",
].forEach((taskName) => {
Meteor.callAsync("tasks.insert", {
text: taskName,
createdAt: new Date(),
userId: user._id
});
});
}
...
```
:::
See that we are using a new field called `userId` with our user `_id` field, we are also setting `createdAt` field.
### 7.7: Task owner
First, let's change our publication to publish the tasks only for the currently logged user. This is important for security, as you send only data that belongs to that user.
::: code-group
```js [/imports/api/TasksPublications.js]
import { Meteor } from "meteor/meteor";
import { TasksCollection } from "./TasksCollection";
Meteor.publish("tasks", function () {
let result = this.ready();
const userId = this.userId;
if (userId) {
result = TasksCollection.find({ userId });
}
return result;
});
```
:::
Now let's check if we have a `currentUser` before trying to fetch any data. Update the reactive `tasks` and `incompleteCount` to only run if logged in:
::: code-group
```jsx [imports/ui/App.jsx]
// ... other imports and code
Tracker.autorun(async () => {
setIsReady(subscription.ready());
if (!Meteor.userId()) { // [!code highlight] // Skip if not logged in
setTasks([]); // [!code highlight]
return; // [!code highlight]
} // [!code highlight]
// Use ReactiveVar in the query for Tracker reactivity
const query = hideCompletedVar.get() ? { isChecked: { $ne: true } } : {};
setTasks(await TasksCollection.find(query, { sort: { createdAt: -1, _id: -1 } }).fetchAsync());
});
// Reactive incomplete count
const [incompleteCount, setIncompleteCount] = createSignal(0);
Tracker.autorun(async () => {
if (!Meteor.userId()) { // [!code highlight] // Skip if not logged in
setIncompleteCount(0); // [!code highlight]
return; // [!code highlight]
} // [!code highlight]
setIncompleteCount(await TasksCollection.find({ isChecked: { $ne: true } }).countAsync());
});
// ... rest of component
```
:::
Also, update the `tasks.insert` method to include the field `userId` when creating a new task:
::: code-group
```js [imports/api/TasksMethods.js]
...
Meteor.methods({
"tasks.insert"(doc) {
const insertDoc = { ...doc };
if (!('userId' in insertDoc)) {
insertDoc.userId = this.userId;
}
return TasksCollection.insertAsync(insertDoc);
},
...
```
:::
### 7.8: Log out
We can also organize our tasks by showing the owner’s username below our app bar. Let’s add a new `div` where the user can click and log out from the app:
::: code-group
```jsx [imports/ui/App.jsx]
...
<div class="main">
<Show
when={currentUser()}
fallback={<Login />}
>
<div class="user" onClick={() => Meteor.logout()}> // [!code highlight]
{currentUser()?.username} 🚪 // [!code highlight]
</div> // [!code highlight]
...
```
:::
Remember to style your username as well.
::: code-group
```css [imports/ui/main.css]
.user {
display: flex;
align-self: flex-end;
margin: 8px 16px 0;
font-weight: bold;
cursor: pointer;
}
```
:::
Phew! You have done quite a lot in this step. Authenticated the user, set the user in the tasks, and provided a way for the user to log out.
Your app should look like this:
<img width="200px" src="/tutorials/solid/assets/step07-login.png"/>
<img width="200px" src="/tutorials/solid/assets/step07-logout.png"/>
In the next step, we are going to learn how to deploy your app!

98
v3-docs/docs/tutorials/solid/8.deploying.md Normal file
View File

@@ -0,0 +1,98 @@
## 8: Deploying
Deploying a Meteor application is similar to deploying any other Node.js app that uses websockets. You can find deployment options in [our guide](https://guide.meteor.com/deployment), including Meteor Up, Docker, and our recommended method, Galaxy.
In this tutorial, we will deploy our app on [Galaxy](https://galaxycloud.app/), which is our own cloud solution. Galaxy offers a free plan, so you can deploy and test your app. Pretty cool, right?
### 8.1: Create your account
You need a Meteor account to deploy your apps. If you don’t have one yet, you can [sign up here](https://cloud.meteor.com/?isSignUp=true).
With this account, you can access our package manager, [Atmosphere](https://atmospherejs.com/), [Forums](https://forums.meteor.com/) and more.
### 8.2: Set up MongoDB (Optional)
As your app uses MongoDB the first step is to set up a MongoDB database, Galaxy offers MongoDB hosting on a free plan for testing purposes, and you can also request for a production ready database that allows you to scale.
In any MongoDB provider you will have a MongoDB URL which you must use. If you use the free option provided by Galaxy, the initial setup is done for you.
Galaxy MongoDB URL will be like this: `mongodb://username:<password>@org-dbname-01.mongodb.galaxy-cloud.io` .
> You can read more about Galaxy MongoDB [here](https://galaxy-support.meteor.com/en/article/mongodb-general-1syd5af/).
### 8.3: Set up settings
If you are not using the free option, then you need to create a settings file. It’s a JSON file that Meteor apps can read configurations from. Create this file in a new folder called `private` in the root of your project. It is important to notice that `private` is a special folder that is not going to be published to the client side of your app.
Make sure you replace `Your MongoDB URL` by your own MongoDB URL :)
::: code-group
```json [private/settings.json]
{
"galaxy.meteor.com": {
"env": {
"MONGO_URL": "Your MongoDB URL"
}
}
}
```
:::
### 8.4: Deploy it
Now you are ready to deploy, run `meteor npm install` before deploying to make sure all your dependencies are installed.
You also need to choose a subdomain to publish your app. We are going to use the main domain `meteorapp.com` that is free and included on any Galaxy plan.
In this example we are going to use `solid-meteor-3.meteorapp.com` but make sure you select a different one, otherwise you are going to receive an error.
> You can learn how to use custom domains on Galaxy [here](https://galaxy-support.meteor.com/en/article/domains-16cijgc/). Custom domains are available starting with the Essentials plan.
Run the deployment command:
```shell
meteor deploy solid-meteor-3.meteorapp.com --free --mongo
```
> If you are not using the free hosting with MongoDB on Galaxy, then remove the `--mongo` flag from the deploy script and add `--settings private/settings.json` with the proper setting for your app.
Make sure you replace `solid-meteor-3` by a custom name that you want as subdomain. You will see a log like this:
```shell
meteor deploy solid-meteor-3.meteorapp.com --settings private/settings.json
Talking to Galaxy servers at https://us-east-1.galaxy-deploy.meteor.com
Preparing to build your app...
Preparing to upload your app...
Uploaded app bundle for new app at solid-meteor-3.meteorapp.com.
Galaxy is building the app into a native image.
Waiting for deployment updates from Galaxy...
Building app image...
Deploying app...
You have successfully deployed the first version of your app.
For details, visit https://galaxy.meteor.com/app/solid-meteor-3.meteorapp.com
```
This process usually takes just a few minutes, but it depends on your internet speed as it’s going to send your app bundle to Galaxy servers.
> Galaxy builds a new Docker image that contains your app bundle and then deploy containers using it, [read more](https://galaxy-support.meteor.com/en/article/container-environment-lfd6kh/).
You can check your logs on Galaxy, including the part that Galaxy is building your Docker image and deploying it.
### 8.5: Access the app and enjoy
Now you should be able to access your Galaxy dashboard at `https://galaxy.meteor.com/app/solid-meteor-3.meteorapp.com`.
You can also access your app on Galaxy 2.0 which is currently in beta at `https://galaxy-beta.meteor.com/<your-username>/us-east-1/apps/<your-app-name>.meteorapp.com`. Remember to use your own subdomain instead of `solid-meteor-3`.
You can access the app at [solid-meteor-3.meteorapp.com](https://solid-meteor-3.meteorapp.com/)! Just use your subdomain to access yours!
> We deployed to Galaxy running in the US (us-east-1), we also have Galaxy running in other regions in the world, check the list [here](https://galaxy-support.meteor.com/en/article/regions-1vucejm/).
This is huge, you have your app running on Galaxy, ready to be used by anyone in the world!

17
v3-docs/docs/tutorials/solid/9.next-steps.md Normal file
View File

@@ -0,0 +1,17 @@
## 9: Next Steps
You have completed the tutorial!
By now, you should have a good understanding of working with Meteor and Solid.
::: info
You can find the final version of this app in our [GitHub repository](https://github.com/meteor/meteor3-solid).
:::
Here are some options for what you can do next:
- Check out the complete [documentation](https://v3-docs.meteor.com/) to learn more about Meteor 3.
- Read the [Galaxy Guide](https://galaxy-support.meteor.com/en/article/deploy-to-galaxy-18gd6e2/) to learn more about deploying your app.
- Join our community on the [Meteor Forums](https://forums.meteor.com/) and the [Meteor Lounge on Discord](https://discord.gg/hZkTCaVjmT) to ask questions and share your experiences.
We can't wait to see what you build next!

BIN
v3-docs/docs/tutorials/solid/assets/collections-connect-db.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 218 KiB

BIN
v3-docs/docs/tutorials/solid/assets/collections-documents.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 189 KiB

BIN
v3-docs/docs/tutorials/solid/assets/collections-see-database.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 153 KiB

BIN
v3-docs/docs/tutorials/solid/assets/collections-tasks-list.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 99 KiB

BIN
v3-docs/docs/tutorials/solid/assets/mermaid-diagram-solid-rendering.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 175 KiB

3
v3-docs/docs/tutorials/solid/assets/mermaid-diagram-solid-rendering.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 18 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step01-dev-tools-mobile-toggle.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 9.9 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step01-mobile-with-meta-tags.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step01-mobile-without-meta-tags.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 17 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step03-form-new-task.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 178 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step03-new-task-on-list.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 184 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step04-checkbox.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 182 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step04-delete-button.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 183 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step05-styles.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 208 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step06-all.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 217 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step06-ddp-messages.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 418 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step06-extension.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 215 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step06-filtered.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 182 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step07-login.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 168 KiB

BIN
v3-docs/docs/tutorials/solid/assets/step07-logout.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 215 KiB

25
v3-docs/docs/tutorials/solid/index.md Normal file
View File

@@ -0,0 +1,25 @@
# Meteor.js 3 + Solid
In this tutorial, we will create a simple To-Do app using [Solid](https://www.solidjs.com/) and Meteor 3.0. Meteor works well with other frameworks like [React](https://react.dev/), [Vue 3](https://vuejs.org/), [Svelte](https://svelte.dev/), and [Blaze](https://www.blazejs.org/).
Solid is a modern UI framework that compiles your reactive code to highly efficient DOM updates at runtime, resulting in smaller bundles and exceptional performance without a virtual DOM. Launched in 2020, it has gained popularity for its fine-grained reactivity, simplicity, and lightweight nature. Compared to older approaches, Solid eliminates much of the boilerplate and runtime overhead found in frameworks like React by using a compiler that optimizes updates precisely where needed. It employs a declarative JSX syntax with built-in primitives like signals for state management, effects, and resources that can be seamlessly integrated with Meteor's reactive data sources like[Tracker](https://docs.meteor.com/api/tracker.html) and [Minimongo](https://docs.meteor.com/api/collections.html). This means your UI updates automatically as data changes, without manual DOM manipulation.
If you're new and not sure what UI framework to use, Solid is a great place to start—it's easy to learn (especially if you're familiar with React-like JSX), highly performant with fine-grained reactivity, and has a growing community. You can still leverage Meteor packages designed for other frameworks, like [accounts-ui](https://docs.meteor.com/packages/accounts-ui), even in a Solid app.
To start building your Solid app, you'll need a code editor. If you're unsure which one to choose, [Visual Studio Code](https://code.visualstudio.com/) is a good option.
Let’s begin building your app!
# Table of Contents
[[toc]]
<!-- @include: ./1.creating-the-app.md-->
<!-- @include: ./2.collections.md-->
<!-- @include: ./3.forms-and-events.md-->
<!-- @include: ./4.update-and-remove.md-->
<!-- @include: ./5.styles.md-->
<!-- @include: ./6.filter-tasks.md-->
<!-- @include: ./7.adding-user-accounts.md-->
<!-- @include: ./8.deploying.md-->
<!-- @include: ./9.next-steps.md-->