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

script-path

v1.0.1

Published

Retrieves the path of the specified script on the page, used to dynamically load assets relative the current script.

Downloads

22

Readme

script-path Build Status

Retrieves the path of the specified script on the page, used to dynamically load assets relative the current script.

Install

npm install script-path --save

Usage

# bundleName is the final name of your bundle (without .min or .js)
var bundleName = 'app';
var scriptPath = require('script-path')(bundleName);

script-path returns the path to the script file as passed in, use it to load assets relative to your bundle, not to the page.

Example

If your page is running at https://example.com/mypage but it's loading your bundle from https://cdn.somewhereelse.com/libs/myscript.min.js, the following code will return https://cdn.somewhereelse.com/libs/.

var scriptPath = require('script-path')('myscript');

Usage with webpack

Webpack enables you to load chunks dynamically from your script, it uses a config setting publicPath (https://github.com/webpack/docs/wiki/Configuration#outputpublicpath) to determine the path to load the chunks from, however this means you either have to load them relative to the current page or know the exact URL at build time. Rather than settings the publicPath property you can include set the path at runtime by assigning it to __webpack_public_path__ on your entry point. Using script-path you don't need to know where it's going to hosted or where it's running from, you can query that at runtime, e.g.

__webpack_public_path__ = require('script-path')('myscript');