npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

vue-window-portal

v1.6.1

Published

Vue component to render content in a new window

Downloads

733

Readme

vue-window-portal

npm version build status

Vue component to render content in a new window.

This works by creating the element in the main window and adding it to the newly created child window, which removes it from the main window. The original window handles all processing and logic of the now-moved component, so no script tags need to be copied over, just styles.

Known limitations

  • Hot-reloading during development will cause the windows to close/open.
  • Styles will not work if your page sets Content Security Policy style-src 'unsafe-inline'. Unfortunately this includes Github Pages.
    • You can get around this by adding an empty _window.html file to your deployed application.
  • Styles cannot hot-reload because they are copied when the window is initially opened.
  • Style/link tags not in document.head will not be copied to the new window (semi-intentional).

Demo

Live demo

Or run locally:

npm run serve

Example usage

See App.vue for a more detailed example.

<template>
  <div>
    Main content

    <vue-window-portal open>
      This content will be rendered in a new window
    </vue-window-portal>
  </div>
</template>

The window can be controlled via its open prop or via the openPortal() and closePortal() methods.

Use the .sync modifier to propagate changes back into your variable, or the @closed event if you only care when the window is closed.

Use the no-style option to avoid copying style tags into the new window.