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

craco-change-public-directory

v1.0.1

Published

Plugin to change the public directory on create-react-app projects using CRACO

Downloads

27

Readme

CRACO Change Public Directory Plugin

This plugin allows you to change the public directory path on your create-react-app project.

It replaces the following CRA configuration settings with your new path:

  • paths.appPublic
  • paths.appHtml

It also does a shallow search and replace on webpackConfig.plugins[*].options for strings that match the old public path.

Usage Example

Install CRACO following the instructions on their documentation: https://www.npmjs.com/package/@craco/craco#installation

Install the plugin using:

npm install -D craco-change-public-directory

Create a craco.config.js containing at the least the following:

const path = require('path');
const changePublicDirectory = require('craco-change-public-directory');

const newPublicPath = path.resolve('your-new-public-directory');

module.exports = {
  plugins: [
    {
      plugin: changePublicDirectory,
      options: {
        newPath: newPublicPath,
      },
    },
  ],
};

Limitations and Known Issues

The way this plugin works is kind of a hack. The purpose of the method overrideWebpackConfig is to return a modified webpack configuration, but we use the same method make changes to the context.paths object received as parameter.

Unfortunately, right now, there's no hook method on CRACO plugin system with the purpose of making changes to the context or context.paths object. This misuse of CRACO plugin API implies that small changes in the future can easily break this plugin functionality.

Also there's a chance that other (CRA/CRACO/Jest/WebPack/...) plugins read the path before our changes are made, or have this paths hardcoded.