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

ensure-url-trailing-slash

v0.1.6

Published

Ensure the current url has a trailing slash

Downloads

115

Readme

ensure-url-trailing-slash

Check if the current URL ends with a trailing slash and redirects to it if not. This will fix site.com/foo into site.com/foo/.

Why?

This is useful for websites deployed on Netlify because site.com/foo and site.com/foo/ will resolve to the same page content. But site.com/foo is considered a file named foo at the root, while site.com/foo/ is considered a file named index.html in the foo/ directory. This has an impact on the way relative paths to assets are handled.

There is currently (as of November 2019) no way to force a redirect from site.com/foo to site.com/foo/ from Netlify, so this module comes as a workaround.

Usage

The main export of the module is a method that will check the URL and redirect (using window.location.replace) if needed.

Note that because of the issue this module is aimed to solve, you shouldn't call the method from an external ressource, as this ressource might not get loaded. Instead, you should inline it in your <head>.

Conveniently, the main export also contains a .source property that contains a stringified version of the method (wrapped in a self-invocated function).

So a typical usage would be to somehow import the module in your build process, then write the .source property in a <script> in your <head>.

head
  script!=ensureUrlTrailingSlash.source

Or, simply copy paste the following minified code into your <head>.

<script>(function(){const{protocol:n,host:o,pathname:t,search:a,hash:h}=window.location;t.endsWith("/")||t.endsWith(".html")||window.location.replace(`${n}//${o}${t}/${a}${h}`)})()</script>