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.