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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Upgrade preact from 8.5.2 to 10.0.1 #6

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Upgrade preact from 8.5.2 to 10.0.1 #6

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade preact from 8.5.2 to 10.0.1.

Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 4 versions ahead of your current version.
  • The recommended version was released 8 days ago, on 2019-10-17.
Release notes
  • Package name: preact
    • 10.0.1 - 2019-10-17

      tl;dr: This is a standard bug-fix release with no new features. We encourage everyone to upgrade

      Wow, we've been overwhelmed with the reactions to our final Preact X release! We saw a huge uptick in npm downloads to 200.000 per week 🎉 Another exciting announcement is that Google AMP is officially using Preact under the hood. We've receivied many more thank you notes (and even stroopwafels!) from companies using Preact. Those range from small companies to big enterprise ones, where Preact is used in a wide span of different environments.

      We preactively allocated the weeks after the big launch for a period of bug-fixes only in case something slipped through. It was admittedly a more conservative decision after our long alpha and beta period, but we wanted to make sure that you all would have a butter smooth experience no matter what 🌠 It's safe to say that it went really well and we've only received a couple bug reports so far 🎉

      In the short amount of time that has passed since the release, we managed to squash a good portion of those! Thank you so much to everyone for reporting bugs and helping us track them down! You rock 👍 💯

      Bug Fixes

      Types

      Maintenance

    • 10.0.0 - 2019-10-01

      preact-x

      tl;dr: Preact X is the next major version of Preact fully packed with features like Fragments, Hooks, componentDidCatch, Test-Utils, Debug-Warnings, many compatibility fixes and so much more 🎉

      It's finally happening! After months of hard work we've crossed the finish line and are over the moon with excitement to finally mark Preact X as stable. We'd like to thank everybody who tested it and submitted bug reports.

      We originally planned to release a sort-of migration release as version 9 with just the breaking changes from X, but that got canned because many users reported that the upgrade process was easy enough and didn't warrant a long migration period in-between. In fact we got many reports that the upgrade could be done in under an hour, despite some of the breaking changes in X, making the need for a migration release even less desirable.

      What's new?

      Preact X ships with several major features and we combined them all in a single document on our site. If you're upgrading an existing Preact 8.x project, we got you covered with a detailed upgrade guide.

      To give a quick summary of the new features:

      • Fragments
      • componentDidCatch
      • preact/hooks addon
      • preact/test-utils addon
      • createContext API
      • compat moved to core
      • Plethora of compatibility fixes
      • Many new warnings in preact/debug
      • Same 3 kB size as Preact 8

      Again, we highly recommend checking out our new site and specifically the what's new section.

      Changes since RC 4

      Bug Fixes

      Typings

      Maintenance

    • 10.0.0-rc.3 - 2019-09-10

      So uhm... just yesterday we've published RC2 and we've mentioned that it would be likely the last RC before going final. Turns out that fate had other plans. One seemingly minor change to our jsx constructor function lead to pretty weird and nasty bug depending on whether the code was run in use strict mode or not. @jviide wrote up a great summary on how this issue came to be.

      Bug Fixes

      Typings

      • Fix PureComponent not passing generic types along (#1920, thanks @amelekhin)
    • 10.0.0-rc.2 - 2019-09-09

      tl;dr: This release contains a lot of bug fixes in many areas and we encourage everyone to upgrade. We're confident that this is the last rc release before marking X as stable.

      It's time for another Preact release 🎉 We've spent the past weeks on make
      Preact as robust as we can. Most fixes are ones you all submitted to our
      tracker. This is super awesome and we wouldn't be where we are without all your
      help!

      On top of countless fixes, a few minor features found their way into the
      package like isValidElement that can be used to check if something is valid to
      render, meaning it's a valid child that was created by h/createElement.

      The test utils also received much love and we're very impressed with how quickly
      @robertknight was able to land support for async callbacks and nested calls
      to act 💯 This is useful in cases where triggering an effect or state change
      involves async steps, such as waiting for a fetch call to resolve.

      Preact Devtools are coming

      We think it'd be good to give a setSate of the union here about where we are
      with the devtools. As many of you are aware we've always depended on the
      react-devtools extension for a long time now. We were very excited to
      integrate with version 4, not just because of the new featureset, but also
      because the adapter and protocol is so much better than before.

      We got very far, but despite of all our efforts we ran into blocker issues with
      the expected order of events that need to be sent to the extension. Our
      internals differ quite a bit and after trying for weeks to get it right we
      ultimately went back to the drawing board.

      It became clear that just writing our own extension would be less resource
      intensive and would make it easier for us to maintain. It's pre-alpha right now,
      but we expect to mature in the coming weeks/month. Here is a screenshot as a
      little sneak peek:

      preact-devtools-preview-public

      Very early pre-alpha preview of preact-devtools

      We'll keep you posted! Here is the full list of changes in this release:

      Features

      Bug Fixes

      Typings

      Maintenance

    • 10.0.0-rc.1 - 2019-08-02

      tl;dr: This release contains many little fixes and we encourage all X users to upgrade.

      As we're nearing closer to the actual release we're hoping to sweeten the wait with another rc-release 🎉 While the docs are coming along nicely we have a preview of our upcoming migration guide to Preact X from 8.x. We have a little polish left to do, but apart from that the new docs are basically ready :fingers_crossed:

      But back to the actual release! This time the fixes touch a broad area in Preact. There are a few for Portals, some for onTransition* or onAnimation* events and the usual round of browser or typing PRs.

      It's arguably less feature packed than previous releases, but that's a really good sign for the release candidate phase. It means that X is mature and is in great shape for going gold 👍 💯

      Features

      • Diff props when replacing a node and don't diff when hydrating (#1786, thanks @JoviDeCroock)

      Bug Fixes

      Typings

      Maintenance

    • 10.0.0-rc.0 - 2019-07-11

      tl;dr: This is mostly a bugfix only release, with one notable exception. Due to popular demand we reversed our decision to remove support for string styles and brought them back 🍀 All users on the next tag are encouraged to upgrade 👍

      You may have already noticed the rc suffix in the release number and that is because we're finally out of beta 👍 rc stands for roughly complete... uh... release candidate and this means that a final Preact X release is really close 🏁 We do wanted to give it another phase of testing before going final though and it gives us a bit time to get our docs in shape.

      8.x will be maintained further 🔧

      Don't worry if there is something you would have loved to see in X, but that didn't make the cut. The final X release is more of a sign that we think it's stable and maybe even more so than 8.x ever was 🎉 This also means that we can focus more on adding new features and reduce our current maintenance overhead of working on two release lines simultaneously. The upgrade should be pretty seamless for everyone and we'll publish a complete migration guide along with the final X release. If you for some reason can't update to X don't worry. We'll keep maintaining the 8.x release line for a good while.

      Now You’re Thinking With Portals

      This release contains some noteworthy fixes to our Portal-Component. But not just that, we also added back support for string styles due to popular demand. Originally we removed them to save bytes, but it turns out that this feature is way to useful not to have. Additionally it aligns better with out philosophy with being "closest to the DOM". Thank you'all for everyone who participated in that journey and helped us make the right decision moving forward 👍 💯

      SSR Boost 🚤

      This change has been cooking for a while and plays well along with the research @developit and @housseindjirdeh have been doing about hydration. When you look at the way SSR works, you'll notice that pretty much the complete diff phase is redundant. The HTML that is sent to the client matches the vnode tree completely, so there isn't much point in comparing changes. The thing is that we can't remove it completely though, because we still need to attach event listeners. For that case we introduced a faster code path which bypasses most of the diffing. After the initial render is done, Preact will continue with the usual diff mode.

      Note: This may be a breaking change if you are sending an incorrect DOM structure to the client and relied on hydrate to correct that for you. To fix this make sure to sent HTML that matches the initial vnode tree on the client.

      Rock solid ecosystem

      At this point we'd like to give a shoutout to @robertknight who continues to quietly maintain enzyme-adapter-preact-pure. It's rock solid already and it's only getting better. Be sure to check it out 🤓

      Without further ado: Here is the full changelog of our first (p)release candidate 🥇

      Features

      Bug Fixes

    • 10.0.0-beta.3 - 2019-06-21

      tl;dr This is a bug-fix-only release and all users are encouraged to update. A final release is in sight 🎉

      It's the summer and while hopefully most of you will be able to enjoy the time
      outside we couldn't pass the opportunity to let our latest beta release free
      into the world! This might be the last beta we'll publish before going gold,
      so stay tuned 😉 For this reason we focused purely on shaking all bugs out
      and make this the most stable preact release we can 👍 💯

      Most notably this includes some rethinking of how we deal with Fragments
      internally. Over the past weeks we received bug reports which all seemed to be
      related and it turns out they were! They all shared the problem that the sibling
      order was different after a component update. We all got our heads together
      and found a better internal implementation for Fragments that's a lot more
      sound theoretically. It should fix all ordering issues for good 👍 🏁

      Although this release is quite and we've set our sights on a final release we're
      already working on getting the Preact debug adapter in shape for the upcoming
      react-devtools v4 🎉 It's not just more performant, but also adds the
      hooks panel right in the devtools. More on that soon 😉

      Again, you are awesome

      As always Preact wouldn't be what it is today without you all. Whether you've
      been helping us squash bugs, joined feature discussions or just spread the word,
      we're really thankful to be part of such an amazing community. We even got to
      meet some of you at this years JSConfEU!

      With all said: We can't wait to unleash the final release soon! If you're new
      to the beta releases, don't worry. The final release will be accompanied with
      a migration guide 👍

      Important

      Because of the internal restructuring preact-render-to-string needs to be updated to at least version 5.0.4.

      Bug Fixes

      Typings

      Maintenance

    • 10.0.0-beta.2 - 2019-05-31 
        </li>
  <li>
    <b>10.0.0-beta.1</b> - <a href="">2019-05-02</a>
    
  </li>
  <li>
    <b>10.0.0-beta.0</b> - <a href="">2019-04-17</a>
    
  </li>
  <li>
    <b>10.0.0-alpha.4</b> - <a href="">2019-04-05</a>
    
  </li>
  <li>
    <b>10.0.0-alpha.3</b> - <a href="">2019-04-02</a>
    
  </li>
  <li>
    <b>10.0.0-alpha.2</b> - <a href="">2019-03-14</a>
    
  </li>
  <li>
    <b>10.0.0-alpha.1</b> - <a href="">2019-03-07</a>
    
  </li>
  <li>
    <b>10.0.0-alpha.0</b> - <a href="">2019-03-04</a>
    
  </li>
  <li>
    <b>8.5.2</b> - <a href="https://github.com/preactjs/preact/releases/tag/8.5.2">2019-08-18</a>
    <p>This release is a maintenance release and all users of the 8.x release line are encouraged to upgrade to it.</p>
      • Fix devtools bridge not working with react devtools v4 (#1876)
    • from [`preact` GitHub Release Notes](https://github.com/preactjs/preact/releases)
------------

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@ajesse11x ajesse11x mentioned this pull request Jan 9, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@snyk-bot