子路径中的扩展

¥Extensions in subpaths

包作者应在其导出中提供扩展 (import 'pkg/subpath.js') 或无扩展 (import 'pkg/subpath') 子路径。这确保每个导出的模块只有一个子路径，以便所有依赖导入相同的一致说明符，使消费者清楚地了解包合同并简化包的子路径的完成。

¥Package authors should provide either extensioned (import 'pkg/subpath.js') or extensionless (import 'pkg/subpath') subpaths in their exports. This ensures that there is only one subpath for each exported module so that all dependents import the same consistent specifier, keeping the package contract clear for consumers and simplifying package subpath completions.

传统上，包倾向于使用无扩展名风格，它具有可读性和掩盖包中文件的真实路径的好处。

¥Traditionally, packages tended to use the extensionless style, which has the benefits of readability and of masking the true path of the file within the package.

随着 导入映射 现在为浏览器和其他 JavaScript 运行时中的包解析提供标准，使用无扩展样式可能会导致导入映射定义膨胀。显式文件扩展名可以避免此问题，方法是使导入映射尽可能利用 包文件夹映射 映射多个子路径，而不是每个包的子路径导出一个单独的映射条目。这也反映了在相对和绝对导入说明符中使用 完整说明符路径 的要求。

¥With import maps now providing a standard for package resolution in browsers and other JavaScript runtimes, using the extensionless style can result in bloated import map definitions. Explicit file extensions can avoid this issue by enabling the import map to utilize a packages folder mapping to map multiple subpaths where possible instead of a separate map entry per package subpath export. This also mirrors the requirement of using the full specifier path in relative and absolute import specifiers.