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
A new version was just released of babel-loader, so Doppins
has upgraded your project's dependency ranges.
Make sure that it doesn't break anything, and happy merging!
Upgraded babel-loader from ^7.1.2 to ^8.0.0
Changelog:
Version 8.0.0
#639 - Use MD4 instead of SHA1 for filename hashes
#644 - Read file before creating directory
#645 - [docs] Update http-links to https
#660 - Pass Babel's .caller option and pass supportsStaticESM:true.
NOTE: For those looking for v8.0.0-beta.5, it was a mis-publish of the wrong branch and included only #660 and missed the other 3 PRs.
Version 8.0.0
#629 Include additional result values from Babel's output for custom loaders
Version 8.0.0
#590 Handle cache directory fallback better
#599 Drop logic for reading the .babelrc and rely on ``@babel/core
#618 Refactor to use async functions for async handling (compiled to generators)
#619 Expose an API for users to create custom wrapper around babel-loader
Version 8.0.0
💥BREAKING CHANGE
Remove forceEnv in favor of the core envName option. (#586) (@loganfsmyth)
The forceEnv option has been removed. You can simple replace it with the new option envName from babel-core. (see https://github.com/babel/babel/tree/master/packages/babel-core#options)
Fix the resolving of babelrc when extends not set (#588) (@danez)
Version 8.0.0
💥BREAKING CHANGE
The babelrc option was changed. It now only accepts true or false as valid option (similar to other babel packages) and does not allow setting a string. If you previously had a filename specified you need to change to extends
doppins-bot
changed the title
[Doppins] Upgrade dependency babel-loader to ^8.0.5
[Doppins] Upgrade dependency babel-loader to ^8.0.6
May 12, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi!
A new version was just released of
babel-loader, so Doppinshas upgraded your project's dependency ranges.
Make sure that it doesn't break anything, and happy merging!
Upgraded babel-loader from
^7.1.2to^8.0.0Changelog:
Version 8.0.0
#639- Use MD4 instead of SHA1 for filename hashes#644- Read file before creating directory#645- [docs] Update http-links to https#660- Pass Babel's .caller option and pass supportsStaticESM:true.NOTE: For those looking for
v8.0.0-beta.5, it was a mis-publish of the wrong branch and included only#660and missed the other 3 PRs.Version 8.0.0
#629Include additional result values from Babel's output for custom loadersVersion 8.0.0
#590Handle cache directory fallback better#599Drop logic for reading the.babelrcand rely on ``@babel/core#618Refactor to use async functions for async handling (compiled to generators)#619Expose an API for users to create custom wrapper aroundbabel-loaderVersion 8.0.0
💥BREAKING CHANGE
Remove forceEnv in favor of the core envName option. (
#586) (@loganfsmyth)The
forceEnvoption has been removed. You can simple replace it with the new optionenvNamefrom babel-core. (seehttps://github.com/babel/babel/tree/master/packages/babel-core#options){ loader: 'babel-loader', options: { - forceEnv: 'staging', + envName: 'staging', }, }🐛 Bug Fix
#588) (@danez)Version 8.0.0
💥BREAKING CHANGE
The
babelrcoption was changed. It now only acceptstrueorfalseas valid option (similar to other babel packages) and does not allow setting a string. If you previously had a filename specified you need to change toextends{ loader: 'babel-loader', options: { - babelrc: 'path/to/.babelrc', + babelrc: false, + extends: 'path/to/.babelrc', }, }🐛 Bug Fix
#550) (@lencioni)@babel/core option check when inputSourceMap null (#538) (@Delagen)#583) (@danez)#584) (@michael-ciniawsky)📝 Documentation
#442) (@jedwards1211)Version 8.0.0
v8.0.0-beta.0
/coreinstead of `babel-core` since we have moved to scoped packages: `https://github.com/babel/babel-loader/pull/522`