simplajs/simpla

Create ES module build

Open

#74 建立於 2017年10月4日

在 GitHub 查看
 (4 留言) (0 反應) (1 負責人)JavaScript (530 star) (38 fork)batch import
enhancementgood first issue

描述

Currently the module field on package.json points to src/simpla.js but really it should point to a separate build, that's been transpiled, but not bundled. This means that whatever module bundling system consumers are using will still be used, but it won't need to be transpiled. As it currently stands, users can come up against this bug but more generally it'll require them to transpile our source, not just bundle it.

An interim measure would be to change where module points to - just the transpiled, bundled simpla.js in root. The main reason behind giving users an ES module target is so they can tree shake, but as we only have one default export, Simpla, this is pretty redundant.

貢獻者指南

技術棧
javascript
領域
build systemrelease
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
npmpackage.json configurationJavaScript module bundler
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
The issue requests creating an ES module build for the simpla package. Currently, the 'module' field points to source, causing consumers to transpile again. The solution is to create a separate transpiled but unbundled build, point 'module' to it. This involves setting up a build script (e.g., with Babel) to output ES modules, and adjusting the package.json. Since there is an assignee, check if any progress exists in linked branches or commits. For a first time contributor, they could examine the existing build configuration and extend it to produce the ES module version.