You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
/** * Created by kukuchong on 2017/11/8. */ const path = require('path'); const webpack = require('webpack'); const HtmlWebpackPlugin = require('html-webpack-plugin'); const ExtractTextPlugin = require('extract-text-webpack-plugin') const CopyWebpackPlugin = require('copy-webpack-plugin'); const config = { context: path.join(__dirname, 'src'), entry: { 'app':'./index.js' }, output: { filename: '[n
We use lerna to seperate concernes into multiple packages. One of them is depending on two others to combine them in the final build. For production we build them independently and then put the dependencies into the node_modules directory of the first package. In development we do nothing special because babel-node from the first package seems to take care of the import statements also from the ot
v7.0.0-rc.3 (2018-08-24) https://twitter.com/left_pad/status/1031700991186489344 😂 💥 Breaking Change babel-preset-env #8509 Add browserslist 4 support.. (@yavorsky) babel-plugin-transform-runtime #8518 Make 'useESModules' only toggle CJS vs ESM helpers when importing file is ESM.. (@loganfsmyth) 🚀 New Feature babel-plugin-transform-runtime #8520 Expose opt-in useESModules:"auto" from transform-
v7.0.0-rc.0 (2018-08-09) EDIT: This had an issue with peerDependencies so please use rc.1. Alright finally at the end 🙂. Shouldn't have anymore breaking changes and going to wait some time to fix bugs/regressions Summary: @babel/polyfill will not include proposal polyfills by default and fixed a regression. 💥 Breaking Change babel-polyfill #8440 remove proposals polyfills from default import [sk
@babel/preset-stage-0 As of v7.0.0-beta.55, we've removed Babel's Stage presets. Please consider reading our blog post on this decision for more details. TL;DR is that it's more beneficial in the long run to explicitly add which proposals to use. For a more automatic migration, we have updated babel-upgrade to do this for you (you can run npx babel-upgrade). If you want the same configuration as b
error: bundling failed: Error: Requires Babel "^7.0.0-0", but was loaded with "6.26.3". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel. (While processing prese
cc @loganfsmyth Feature change request Input Code N/A Babel/Babylon Configuration (.babelrc, package.json, cli command) Anything with passPerPreset Expected Behavior The use of passPerPreset should be restricted Current Behavior passPerPreset is allowed in user configurations Possible Solution Disallow using passPerPreset in user Babel configurations. Context The majority of current usages of pass
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く