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-nodegui

v1.0.0-alpha.1

Published

NodeGUI but with Vue

Downloads

7

Readme

vue-nodegui

NodeGUI but with Vue

This is a work in progress that uses Vue 3 to implement. View the example project using vue-nodegui

Contribution Guide / Goals

If you want to contribute to this project please note the current goals and objectives this project wants to obtain.

  • Feature parity and similarity with HTML/JS in the web, writing applications should not feel any different from writing native HTML & JS for the web.
    • Examples
      • <input> will on-the-fly rebuild the native widget when type is changed rather than substituting custom element types (e.g. no <checkbox> or <radio> element use type="radio/checkbox")
      • <div> & <span> instead of <view> (like react-nodegui) to create a QWidget container
  • JavaScript API should be the same where possible to the DOM API
  • CSS goals, while mostly application dependent, still stand how the structure should be
    • .vue files with <style> should translate to a single CSS file that is loaded by the application to Window.styleSheet (global to the window)
    • .vue Scoped style via <style scoped> is not currently a goal as it may be more tricky to support.

Design choices are open for discussion and if you have anything you'd like to contribute please open an issue (or if one exists comment on that) to create or add to a discussion around a specific design of something.