keystonejs/keystone-classic

babel settings in root directory are used for keystone module

Open

#4,488 建立於 2017年10月30日

在 GitHub 查看
 (4 留言) (1 反應) (0 負責人)JavaScript (14,656 star) (2,288 fork)batch import
bughelp wanted

描述

Expected behavior

Admin.js should not fail with errors

Actual/Current behavior

When using the transform-runtime plugin for babel admin.js crashes with

TypeError: $export is not a function

as babel-polyfill is reading .babelrc or package.json.

Steps to reproduce the actual/current behavior

create a babelrc file with plugin: transform-runtime

Environment

Software Version
Keystone 4.0.0-beta.7
Node 6.10

貢獻者指南

技術棧
javascriptnodejs
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of Babel configurationFamiliarity with Node.js module resolutionUnderstanding of Keystone admin.js build processAbility to test changes locally
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The issue occurs when a user's .babelrc file with transform runtime plugin conflicts with Keystone's admin.js build. Investigate how Keystone loads Babel configuration; likely the admin module inherits root .babelrc settings. Check the Keystone repository for its own Babel config (e.g., in `admin/` or `keystone/` packages). Consider isolating the admin module's Babel config using `env` or a custom `.babelrc` that overrides root settings. Reproduce the bug by creating a test project with transform runtime and running admin.js. Look at the keystone classic source code for babel configuration to identify the exact files involved.