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

fix-insensitive-import

v1.0.4

Published

fix insensitive import caused by FS like windows

Downloads

5

Readme

Fix insensitive imports in Javascript caused by FS like windows

Fix insensitive import in Javascript/typescript caused by insensitive filesystems like Windows.
When working on a project utilizing a JavaScript framework such as Angular on a Windows system, you may encounter an issue with case-insensitive imports.
This becomes especially problematic when deploying on a sensitive file system like Ubuntu, requiring tedious and frustrating manual fixes for each file. The primary goal of the project is to address this issue by dynamically resolving imports based on the actual filename where they are imported from.

Install

npm install fix-insensitive-import

Usage & Api

  • 1 Create an instance of the FixInsencitiveImport :
    the configuration is very sample , you just need to configure the target directory where the library will handle the files, by default the library create a log directory named "fix_insencitive_import_logs" where the logs are stored you can disable the logs by setting the shouldLog to false

 import  { FixInsencitiveImport }  from "fix-insensitive-import";

const fixInsencitiveImport = new FixInsencitiveImport({
    targetDir : "./sample",
    shouldLog : false 
})

fixInsencitiveImport.execute();

If you want to handle just a specefic file names for example the files that end with ".component.ts", you can add a file handle rule


 fixInsencitiveImport.addHandleFileRule(function(filename){
     return filename.includes(".component.js")
 })

 fixInsencitiveImport.execute();