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

Update dependency page to v1.11.4 #10779

Closed
wants to merge 1 commit into from
Closed

Update dependency page to v1.11.4 #10779

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 2, 2018

This PR contains the following updates:

Package Type Update Change References
page dependencies minor 1.7.1 -> 1.11.4 source

Release Notes

visionmedia/page.js

v1.11.4

Compare Source

This is a patch release, fixing an issue with pushState use within the file:// protocol.

v1.11.3

Compare Source

Fixes a regression with options being passed into start()

v1.11.2

Compare Source

Fixes a bad build that was created in 1.11.1

v1.11.1

Compare Source

This is a patch release, fixing a bug with the page instance being configured twice when page.create() is used. Specials thanks to @​jsnajdr for this bug fix. Pull request

v1.11.0

Compare Source

This is a minor release that adds the clickHandler property.

v1.10.2

Compare Source

This is a patch release, fixing #​501

v1.10.1

Compare Source

This is a patch release, fixing an issue from when clicking a link from within a page with query parameters, and navigating to the same page (such as a hash). Previously the querystring was not included in the Context object. This fixes that.

v1.10.0

Compare Source

This is a minor release, adding the new page.create() API, for creating distinct page objects.

Calling page.create(options) create a new page function that behaves just like the global page. It contains its own internal state, options, and event handlers. You can target the page to another window, like an iframe or a popup, if you want.

var newPage = page.create({
  window: someIframe.contentWindow
});

The main reason for adding this feature was to clean up or testing infrastructure. Numerous things had to be done in the past to make sure each test was cleanly in isolation. That stuff is no longer necessary now that we can just create a new page instance for each test.

v1.9.0

Compare Source

This is a minor release, adding a new ES module bundle to the distributed package. This module is available as page.mjs. It contains one export, the default export which is the usual page object.

<script type="module">
  import page from "//unpkg.com/page/page.mjs";

  page('/home', () => {
    showHome();
  });
  page();
</script>

v1.8.6

Compare Source

v1.8.5

Compare Source

v1.8.4

Compare Source

v1.8.3

Compare Source

==================

This is a patch release which switches the build to rollup. Switching shaves 2k off of the gzipped size. In addition to this benefit, this also fixes a couple of small issues:

Issues

v1.8.2

Compare Source

==================

This is a patch release fixing an issue that was meant to be solved in 1.8.1. page.js now runs in Node.js again, when there isn't a window environment.

v1.8.1

Compare Source

==================

This is a patch release, fixing an issue with Node.js usage.

v1.8.0

Compare Source

==================

This is a minor release, adding one new (minor) feature and a few bug fixes and documentation improvements.

Controlling other pages

The new feature of this release is that page.js can now control other pages (windows) besides the main window. This makes it possible to control an iframe's routing. You can use it by passing the window option to start:

page('/', function(){
  // Whoa, I'm inside an iframe!
});

page.start({ window: myiFrame.contentWindow });

Note that page is still a singleton, which means you can only have 1 page, so you can't control both an iframe and the main window at the same time.

This change was made to improve our testing, but in the future we'll make it possible to have multiple page objects so you really will be able to control multiple iframes and the main window all at the same time.

Better hashbang support

Hashbang support has never been very good in page.js. But we're slowly improving it! In 1.8.0 we've fixed the problem where the app's full URL would show up in the hashbang upon start. http://example.com/my/page#!/my/page. Gross! No longer happens thanks to #​447.

Pull Requests

Those are the big things, but here's a list of all of the pull requests merged into 1.8.0:

  • #​445 - Prevent hash from being part of the ctx.pathname
  • #​447 - Prevent going to the root when setting up the initial hashchange route
  • #​446 - Add a note about usage with a CDN
  • #​443 - Change test infrastructure to run inside of iframes
  • #​303 - page.exit callback example missing context param
  • #​267 - Added clarification for decoded plus signs in urls

v1.7.3

Compare Source

==================

This is a patch release making an improvement to how page.js works on pages that use the file protocol, such as Electron and nw.js apps.

Pull Requests

  • #​441 - Set the page's base to be the current location when used under the file protocol with hashbang routing.

v1.7.2

Compare Source

==================

Our first release in almost 2 years! This is a long overdue patch release that contains various bug fixes that have taken place over the course of the last couple of years. As releases will become much more often in the future (containing only a few fixes in most cases), I will be listing the closed issues in releases, but because there are 2 years worth it is not practical to do so in this release.

While you're here, if you haven't checked out page.js in a long time now is a great time. I've recently taken over maintenance and have a plan in place to take this great small library into the future. For now I am concentrating on stabilizing 1.x by fixing as many of the backlog of issues that have built up as I can. Once that is complete we'll start thinking about 2.0.

If you've submitted a PR here in the past and seen it be ignored, please come back! Your contributions are invaluable, and I promise that as long as I'm maintaining this project I'll do my best to always at least comment on pull requests and try to get them resolved.

That's all for now! Please report any issues you find in 1.7.2.


Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot. View repository job log here.

@renovate renovate bot requested a review from a team December 2, 2018 09:02
@renovate renovate bot added [Status] Needs Review To request a review from Crew. Label will be renamed soon. [Type] Janitorial labels Dec 2, 2018
@jetpackbot
Copy link

jetpackbot commented Dec 2, 2018

Warnings
⚠️ "Testing instructions" are missing for this PR. Please add some
⚠️ "Proposed changelog entry" is missing for this PR. Please include any meaningful changes

This is an automated check which relies on PULL_REQUEST_TEMPLATE. We encourage you to follow that template as it helps Jetpack maintainers do their job. If you think 'Testing instructions' or 'Proposed changelog entry' are not needed for your PR - please explain why you think so. Thanks for cooperation 🤖

Generated by 🚫 dangerJS against c3433be

@renovate renovate bot force-pushed the renovate/page-1.x branch 2 times, most recently from 9f2b1fb to 692e594 Compare December 3, 2018 23:03
@oskosk oskosk changed the title Update dependency page to v1.11.3 rebase! Update dependency page to v1.11.3 Dec 4, 2018
@renovate renovate bot changed the title rebase! Update dependency page to v1.11.3 Update dependency page to v1.11.3 Dec 4, 2018
@brbrr
Copy link
Contributor

brbrr commented Dec 13, 2018

Some internal discussion and attempts to resolve it: CBG1CP4EN/p1544445965249000-slack-jetpack-crew

@renovate renovate bot changed the title Update dependency page to v1.11.3 Update dependency page to v1.11.4 Jan 29, 2019
@renovate renovate bot changed the title Update dependency page to v1.11.4 fix(deps): update dependency page to v1.11.4 Feb 4, 2019
@renovate renovate bot changed the title fix(deps): update dependency page to v1.11.4 Update dependency page to v1.11.4 Feb 5, 2019
@dereksmart dereksmart added [Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! and removed [Status] Needs Review To request a review from Crew. Label will be renamed soon. labels Feb 20, 2019
@renovate renovate bot force-pushed the renovate/page-1.x branch 2 times, most recently from 7ba6bcf to d3ad027 Compare March 29, 2019 05:04
@renovate renovate bot closed this May 7, 2019
@renovate renovate bot deleted the renovate/page-1.x branch May 7, 2019 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Needs Author Reply We would need you to make some changes or provide some more details about your PR. Thank you! Touches WP.com Files [Type] Janitorial
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants