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

node-loader-relative

v0.0.3

Published

Loader for Node native extensions resolve relative path situation

Downloads

2,580

Readme

Node Loader For Relative Path

Package for loading native files in Node and Electron applications. The project is inspired by the native-ext-loader. It works in the similar way but allows to build relative path at runtime.

Installation

Add the package to the development dependencies:

# using npm:
$ npm install node-loader-ralative --save-dev

# using yarn:
$ yarn add --dev node-loader-ralative

Usage

Update rules entry in the Webpack configuration file: (same as node-loader)

module: {
  rules: [
    {
      test: /\.node$/,
      loader: "node-loader-ralative"
    }
  ];
}

Options

Options are configurable using options hash:

module: {
  rules: [
    {
      test: /\.node$/,
      loader: "node-loader-ralative",
      options: {
        basePath: __dirname
      }
    }
  ];
}

basePath (default: undefined)

It allows to set a path that will be the basic webpack config path to load native files.

Note that, when undefined, there is no different with node-loader; when path setted(usually it is __dirname, also the webpack config path), this package will calculate out the relative path from the param path, by path.relative in node native module and load correctly.

If any error is cached, you could log filePath manually to check it.

Releasing a new version

  1. Bump version number in the package.json and CHANGELOG.md files.
  2. Run npm install to update package-lock.json file.
  3. Commit changes (include changes)
  4. Add a new tag (use -a and include changes)
  5. Push commits and tag
  6. Run npm publish