emberjs/ember.js

Omit code for optional features that are turned off

Open

#18,710 创建于 2020年1月29日

在 GitHub 查看
 (4 评论) (0 反应) (0 负责人)JavaScript (22,437 star) (4,216 fork)batch import
Help Wanted

描述

Talked to @pzuraq and he mentioned that it's theoretically possible to strip out ember-source code that won't be used due to optional-features. This tooling would be great incentive for apps to invest in moving in the direction the core team/communities deems as the way forward.

Not sure where this would happen, but opening here since it seems like a build time concern

(Reopening https://github.com/ember-cli/ember-cli/issues/9021)

贡献者指南

技术栈
javascript
领域
build systemdeveloper experience
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
over 1 week
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Familiarity with Ember.js build systemUnderstanding of optional features
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
This issue proposes stripping out ember source code for disabled optional features at build time. Review the prior discussion in ember cli#9021 and consult @pzuraq's input. The implementation likely involves modifying the build tooling (ember cli) to analyze the optional features configuration and tree shake or omit relevant code. Investigate how optional features are currently handled in the ember.js repository, particularly in the `packages` directory, and consider the feasibility of adding a build step.