emberjs/ember.js

Omit code for optional features that are turned off

Open

#18,710 opened on 2020年1月29日

GitHub で見る
 (4 comments) (0 reactions) (0 assignees)JavaScript (22,437 stars) (4,216 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.