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

next-electron-server

v1.0.0

Published

Serve your Next.js app inside Electron using a custom scheme.

Downloads

198

Readme

Next.js Electron Server

Serve your Next.js app inside Electron using a custom scheme.

Install

$ npm install next-electron-server

or using yarn

$ yarn add next-electron-server

Usage

const serveNextAt = require("next-electron-server");

serveNextAt("next://app");

app.on("ready", async () => {
  const mainWindow = new BrowserWindow({
    width: 800,
    height: 600,
  });

  mainWindow.loadURL("next://app");
  // mainWindow.loadURL("next://app/page1");
  // mainWindow.loadURL("next://app/page2");
});

For more infos check out the example directory.

Motivation

Most electron tutorials recommend using a url switch to differentiate between devserver localhost urls in development and static urls used in production:

app.on("ready", async () => {
  const mainWindow = new BrowserWindow({
    width: 800,
    height: 600,
  });

  const url = isDev
    ? "http://localhost:8000"
    : format({
        pathname: join(__dirname, "../renderer/out/index.html"),
        protocol: "file:",
        slashes: true,
      });

  mainWindow.loadURL(url);
});

From my point of view this approach has many drawbacks.

  • The origin of the html document differs between production & development
  • The security model may differ between production & development
  • Paths differ between production & development
  • 404 pages won't work in production

That's why I created next-electron-server. The render page will always being served using the same protocol and url.

  • In development is implements a proxy to http://localhost:3000.
  • In production is serves files from the /out directory.

Features

  • supports 404 pages
  • works with Next.js dev-server
  • waits for Next.j dev-server to start
  • works with paths of images and other static resources
  • static paths won't differ between development and production
  • has zero dependencies

API

serveNextAt(uri, options)

uri

Required
Type: string
Example: next://app

The entry-point of your Next.js app.

options

Type: object

↳ outputDir

Type: string
Default: "./out"

The directory to serve, relative to the app root directory.

↳ port

Type: number
Default: 3000

The port your Next.js dev-server runs on.

↳ dev

Type: boolean
Default !app.isPackaged

This flag decides how to serve the files. When dev === true a proxy will be created pointing to localhost:3000.

↳ privileges

Type: object

Check out electron/docs/protocol for more infos about this config object.

↳ partition

Type: string
Default: electron.session.defaultSession

The partition the protocol should be installed to, if you're not using Electron's default partition.

Contributing

  1. Fork this repository to your own GitHub account and then clone it to your local device
  2. Link it to the global module directory: yarn link
  3. Install in your local project using yarn link next-electron-server

Author

Henrik Wenz (@HenrikWenz)