-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support plugin/preset definitions without prefixes in .babelrc #303
Comments
It would also be awesome if this issue had a 'hacktoberfest' label :). |
Good catch, +1 from me on this issue 👍 |
You're right @tizmagik, this will most likely be moot when 0.4.0 comes out since we're leaning on the monorepo/babel plugin pull request that @jaredmcdonald is working on. Let's merge this change and release it in 0.3.1 in case users bump up against this problem in the interim. |
we'll probably need to do something like this when we support user |
* master: (35 commits) creates local copies of packages so e2e tests use latest code (#345) adds style and script linter packages (#344) now using npm version to check for kyt-cli updates (#337) Adds kyt version option to setup command (#343) make lint-script command; lint now runs scripts and style (#339) Adds bootstrap scripts (#341) fixes test coverage command (#342) Run test from root directory (#336) Monorepo (#330) [ci skip] document Jest/Watchman issue and common workaround (#334) Catch SIGINT (#332) Fixes e2e tests (#326) Removes deprecated reflect eslint rule (#325) Upgrade Linter dependencies (#289) [doc]fix path of eslintrc and stylelintrc (#321) Update unit tests for changes made to resolve #303 (#318) adds ISSUE_TEMPLATE (#317) Adds rfc template (#316) document possible kyt setup repository url formats (#314) Overwrites default npm init test script on setup (#293) ... # Conflicts: # .travis.yml # e2e_tests/tests/cli.test.js # package.json # packages/kyt-cli/cli/actions/setup.js
We currently cannot specify babel plugins and presets without the
babel-*
prefix inconfig/babel.js
because of the way they are resolved. This is a standard convention that's highlighted in the babel docs for a given plugin or preset (see these babel-preset-react docs as an example).The text was updated successfully, but these errors were encountered: