Skip to content
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

[email protected] breaks build ⚠️ #1883

Merged
merged 1 commit into from
Feb 10, 2016

Conversation

greenkeeperio-bot
Copy link
Contributor

Hello 👋

⚠️⚠️⚠️

core-js just published its new version 2.1.0, which is covered by your current version range. After updating it in your project the build kept failing.

This means it’s possible that your software is malfunctioning, because of this update. Use this branch to work on adaptions and fixes.

Happy fixing and merging 🌴


GitHub Release

  • API:
    • ES5 polyfills are split and logic, used in other polyfills, moved to internal modules
      • All entry point works in ES3 environment like IE8- without core-js/(library/)es5
      • Added all missed single entry points for ES5 polyfills
      • Separated ES5 polyfills moved to the ES6 namespace. Why?
        • Mainly, for prevent duplication features in different namespaces - logic of most required ES5 polyfills changed in ES6+:
          • Already added changes for: Object statics - should accept primitives, new whitespaces lists in String#trim, parse(Int|float), RegExp#toString logic, String#split, etc
          • Should be changed in the future: @@species and ToLength logic in Array methods, Date parsing, Function#bind, etc
          • Should not be changed only several features like Array.isArray and Date.now
        • Some ES5 polyfills required for modern engines
      • All old entry points should work fine, but in the next major release API can be changed
    • Object.getOwnPropertyDescriptors moved to the stage 3, January TC39 meeting
    • Added umd option for custom build process, #169
    • Returned entry points for Array statics, removed in 2.0, for compatibility with babel 6 and for future fixes
  • Deprecated:
    • Reflect.enumerate deprecated and will be removed from the next major release, January TC39 meeting
  • New Features:
    • Added Reflect metadata API as a pre-strawman feature, #152:
      • Reflect.defineMetadata
      • Reflect.deleteMetadata
      • Reflect.getMetadata
      • Reflect.getMetadataKeys
      • Reflect.getOwnMetadata
      • Reflect.getOwnMetadataKeys
      • Reflect.hasMetadata
      • Reflect.hasOwnMetadata
      • Reflect.metadata
    • Implementation / fixes Date#toJSON
    • Fixes for parseInt and Number.parseInt
    • Fixes for parseFloat and Number.parseFloat
    • Fixes for RegExp#toString
    • Fixes for Array#sort
    • Fixes for Number#toFixed
    • Fixes for Number#toPrecision
    • Additional fixes for String#split (RegExp#@@split)
  • Improvements:
    • Correct subclassing wrapped collections, Number and RegExp constructors with native class syntax
    • Correct support SharedArrayBuffer and buffers from other realms in typed arrays wrappers
    • Additional validations for Object.{defineProperty, getOwnPropertyDescriptor} and Reflect.defineProperty
  • Bug Fixes:
    • Fixed some cases Array#lastIndexOf with negative second argument

And, as I wrote, I stop active core-js development before finding related work. I already have no money for repairing my PC :) If you wanna progress in core-js - feel free contribute to the project or propose me a good work.


The new version differs by 78 commits .

  • bd87b8b 2.1.0
  • bc84e13 [build] little improvementlibraryoption inbuildgrunt task
  • 1ec488d [build] renameexportCore->umdoption, add it tobuildgrunt task, #169
  • 51e226d add entry points array methods for legacy code and future fixes
  • 16bed76 correct supportSharedArrayBufferand buffers from other realms in typed arrays wrappers
  • b98a792 Merge pull request #169 from suchipi/allow_no_export_in_build
  • dbf2467 Allow user to specify that built output should not export core
  • d3736e5 [devDependencies] updatequnit``
  • d49f103 ``Number#{toFixed, toPrecision} thisNumberValue` fails in old V8 ~ Android 4.3-`
  • e79398e [tests] FF allow negativeNumber#toFixedarguments and the spec allow extended implementations
  • aabe858 addNumber#toFixed, #156
  • b21f3bd [tests] more universal testReflect.constructwith native constructors
  • 8f939d5 [tests] add comments toNumber#toPrecisiontests
  • b4404bd addNumber#toPrecision, #156
  • 32aa7c2 [tests] removeObject.getOwnPropertySymbolshard dependency from some native tests

There are 78 commits in total. See the full diff.


This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡

@dignifiedquire dignifiedquire merged commit e697a2a into master Feb 10, 2016
@dignifiedquire dignifiedquire deleted the greenkeeper-core-js-2.1.0 branch February 10, 2016 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants