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.