meteor-community-packages

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Meteor community packages

Meteor社区包

Use Meteor's community package pages as a curated discovery catalog. A listing does not make a package part of Meteor core, transfer its maintenance to the Meteor organization, or guarantee compatibility with every Meteor 3 release. Select a package only after checking its ownership, current release, supported Meteor range, and changes to application behavior.

This skill owns package discovery, comparison, first adoption, and the package-specific integration documented in Meteor core. It does not replace the core skill for methods, publications, Mongo, accounts, security, testing, builds, or deployment.

将Meteor的社区包页面作为精选的发现目录。包的上架并不代表它属于Meteor核心，也不会将其维护权转移至Meteor组织，更不保证与每个Meteor 3版本兼容。选择包之前，务必检查其所有者、当前版本、支持的Meteor版本范围以及对应用程序行为的变更。

本技能负责包的发现、对比、首次采用，以及Meteor核心文档中记录的包特定集成。它不会替代处理methods、publications、Mongo、accounts、安全、测试、构建或部署的核心技能。

Decision flow

决策流程

Define the missing capability and the behavior that must remain unchanged. Distinguish a new adoption from a package that stopped resolving during a Meteor upgrade. Route the latter to
```
migrate-to-meteor-3
```
.
Inspect
```
.meteor/release
```
,
```
.meteor/packages
```
,
```
.meteor/versions
```
,
```
package.json
```
, and the npm lockfile. Package APIs follow the resolved package version, not only the Meteor release.
Read
```
references/package-catalog.md
```
when the request matches the documented catalog or a promoted package. Open only the selected package's local guide and read its baseline, selection rules, and required checks before responding. Then consult its linked upstream repository for APIs or versions beyond Meteor's maintained guidance.
Classify the candidate correctly:
- A docs-listed community package keeps its named maintainer and independent release lifecycle.
- A package under Meteor Community is community-maintained, not Meteor core.
- A promoted core package, such as
```
roles
```
  in Meteor 3.1+, uses the core package name and Meteor documentation.
Compare behavior, not feature labels. Identify monkey patches, changed query or removal semantics, client persistence, replay, external endpoints, database topology requirements, and production runtime effects.
Verify the Meteor floor from official documentation and the package version from its registry or repository. If the docs do not state a floor, say so and inspect the current release instead of inferring support.
Install through the package's documented ecosystem. Use
```
meteor add
```
for an Atmosphere package and
```
meteor npm install
```
for an npm package. Do not invent a version constraint. After installation, confirm the resolved version in
```
.meteor/versions
```
or the npm lockfile.
Apply every relevant required check from the selected package guide. Do not stop after asking for a project path. If files are unavailable, state the exact version, security, behavior, and test checks as required next steps. For an option not covered there, verify the resolved version against the upstream repository instead of extrapolating from another release.
Add the smallest representative integration and test its package-specific behavior plus the underlying Meteor invariants. Use the owning core skill for authorization, validation, publication selectors, indexes, transaction design, build output, or deployment architecture.

明确缺失的功能以及必须保持不变的行为。区分首次采用包与Meteor升级过程中无法解析的包，后者需路由至
```
migrate-to-meteor-3
```
技能。
检查
```
.meteor/release
```
、
```
.meteor/packages
```
、
```
.meteor/versions
```
、
```
package.json
```
以及npm锁文件。包API遵循已解析的包版本，而非仅遵循Meteor版本。
当请求涉及文档收录的目录或推广包时，阅读
```
references/package-catalog.md
```
。在回复前，仅打开所选包的本地指南，阅读其基准信息、选择规则和必要检查项。然后查阅其链接的上游仓库，获取超出Meteor维护指南范围的API或版本信息。
正确分类候选包：
- 文档列出的社区包保留其指定维护者和独立的发布生命周期。
- Meteor Community旗下的包由社区维护，不属于Meteor核心。
- 如Meteor 3.1+中的
```
roles
```
  这类推广核心包，使用核心包名称和Meteor官方文档。
对比行为而非功能标签。识别猴子补丁、查询变更或移除语义、客户端持久化、重放、外部端点、数据库拓扑要求以及生产运行时影响。
从官方文档验证最低支持的Meteor版本，并从其注册表或仓库验证包版本。如果文档未说明最低版本，请明确说明，并检查当前版本而非推断支持情况。
通过包的文档化生态系统进行安装。对于Atmosphere包使用
```
meteor add
```
，对于npm包使用
```
meteor npm install
```
。不要自行设定版本约束。安装后，在
```
.meteor/versions
```
或npm锁文件中确认已解析的版本。
应用所选包指南中的所有相关必要检查项。不要仅询问项目路径就停止。如果文件不可用，请明确说明所需的下一步操作，包括具体的版本、安全、行为和测试检查。对于指南未涵盖的选项，验证已解析版本与上游仓库的一致性，而非从其他版本推断。
添加最小化的代表性集成，并测试其包特定行为以及底层Meteor不变量。对于授权、验证、发布选择器、索引、事务设计、构建输出或部署架构，请使用对应的核心技能。

Ecosystem choice

生态系统选择

Use an Atmosphere package when the capability depends on Meteor packages, client/server packaging, Meteor build plugins, package globals, or the Meteor constraint solver. Use npm for general JavaScript libraries and packages designed for the npm ecosystem. A Meteor app can use both.

Atmosphere and Packosphere expose package metadata. Packosphere's maintenance signals help with triage, but they do not replace checking the source repository, release history, open compatibility issues, license, and resolved version.

Useful inspection commands:

bash

meteor --version
meteor show <atmosphere-package>
meteor list
meteor npm view <npm-package> version

当功能依赖于Meteor包、客户端/服务器打包、Meteor构建插件、包全局变量或Meteor约束求解器时，使用Atmosphere包。对于通用JavaScript库和专为npm生态系统设计的包，使用npm。Meteor应用可以同时使用两者。

Atmosphere和Packosphere会暴露包元数据。Packosphere的维护状态信号有助于分类处理，但不能替代检查源代码仓库、发布历史、未解决的兼容性问题、许可证和已解析版本。

实用检查命令：

bash

meteor --version
meteor show <atmosphere-package>
meteor list
meteor npm view <npm-package> version

Adoption checks

采用检查

For every selected package, the response MUST report:

Why it fits better than the documented alternatives.
Who maintains it and whether it is community-maintained or core.
How to verify the current upstream release and resolved package version, plus the documented Meteor boundary.
Which application semantics it changes.
Which data, endpoints, or server capabilities it exposes.
How to remove or roll back the integration.
The concrete focused tests from the selected guide that prove the intended behavior and its security boundary.

Treat wrappers as extensions, not replacements for Meteor's security model. Method and publication helpers still require server authorization and argument validation. Client persistence still requires least-privilege data selection. External method bridges require an explicit exposure and authentication review. For Wormhole or another external method bridge, the response MUST include a pre-exposure checklist covering method inventory, existing authentication and authorization, input validation, rate limits, side effects, returned fields, credential tests, and proof that unexposed methods remain unreachable.

对于每个选定的包，回复必须包含以下内容：

为什么它比文档中的替代方案更合适。
维护者是谁，以及它是社区维护还是核心维护。
如何验证当前上游版本和已解析的包版本，以及文档中记录的Meteor版本边界。
它会改变哪些应用程序语义。
它会暴露哪些数据、端点或服务器功能。
如何移除或回滚集成。
所选指南中的具体聚焦测试，以证明预期行为及其安全边界。

将包装器视为扩展，而非Meteor安全模型的替代品。方法和发布助手仍需服务器授权和参数验证。客户端持久化仍需最小权限的数据选择。外部方法桥接需要明确的暴露和身份验证审查。对于Wormhole或其他外部方法桥接，回复必须包含暴露前的检查清单，涵盖方法清单、现有身份验证和授权、输入验证、速率限制、副作用、返回字段、凭证测试，以及未暴露方法仍不可访问的证明。

Routing

路由

Request	Owning skill
Package does not resolve, build, or support Meteor 3 during an upgrade	`migrate-to-meteor-3`
Method implementation, validation, optimistic UI, or rate limiting	`meteor-methods`
Publication design, authorization, or reactive data semantics	`meteor-pubsub`
Collection selectors, indexes, Change Streams, or Mongo behavior	`meteor-mongo-minimongo`
Accounts and authorization design, including how roles protect server actions	`meteor-accounts` and `meteor-security`
Cluster topology or production rollout	`meteor-deployment`
Publishing or maintaining an Atmosphere package	Package authoring workflow, not this skill

请求	所属技能
升级过程中包无法解析、构建或支持Meteor 3	`migrate-to-meteor-3`
方法实现、验证、乐观UI或速率限制	`meteor-methods`
发布设计、授权或响应式数据语义	`meteor-pubsub`
集合选择器、索引、变更流或Mongo行为	`meteor-mongo-minimongo`
账户和授权设计，包括roles如何保护服务器操作	`meteor-accounts` 和 `meteor-security`
集群拓扑或生产部署	`meteor-deployment`
发布或维护Atmosphere包	包创作工作流，非本技能

Anti-patterns

反模式

Recommend a package only because it appears in Meteor documentation.
Treat Meteor Community ownership as Meteor core support.
Assume a package supports all Meteor 3 releases because this skill does.
Copy the latest API without checking the installed package version.
Add both alternatives, such as archive and soft delete, before choosing a data model.
Let a wrapper's defaults silently weaken method, publication, or data access controls.
Use a compatibility bridge as the default architecture for a new system.

仅因包出现在Meteor文档中就推荐它。
将Meteor Community的所有权视为Meteor核心支持。
假设本技能支持所有Meteor 3版本，因此该包也支持所有Meteor 3版本。
不检查已安装的包版本就直接复制最新API。
在选择数据模型之前同时添加两种替代方案，比如归档和软删除。
让包装器的默认设置悄悄削弱方法、发布或数据访问控制。
将兼容性桥接作为新系统的默认架构。

另请参阅

```
references/package-catalog.md
```
```
references/eval-cases.md
```

```
references/package-catalog.md
```
```
references/eval-cases.md
```