MohammadYounes / MohammadYounes/rtlcss

rtlcss: invalid config file. Error: ENOENT: no such file or directory, stat 'D:\Users\myusername'

Open
#352 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.7k
Forks
124
PR merge metrics
No merged PRs in 30d

Description

Hello,

I'm on Windows 10 Pro.
Two drives, C: and D:
OS and rtlcss are installed in C:
Projects stored in D:
I've configured rtlcss in my IDE and the command line results as:

cmd.exe /D /C call C:\Users\myusername\AppData\Roaming\npm\rtlcss.cmd D:\Project\style.css D:\project\style-rtl.css

The output is:

- rtlcss: invalid config file. Error: ENOENT: no such file or directory, stat 'D:\Users\myusername'
! rtlcss: Warning! No config present, using defaults.
+ Saving:
+ D:\Project\style-rtl.css

It basically looks up for the OS user folder in the same drive as the project is stored ( D: ), not in the drive the OS is installed in ( C: )

The output file is created correctly anyway, but the console gets shown everytime because of the error above.
I suppose I could create an empty directory just to make it happy, but...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the documented rtlcss.cmd invocation on Windows with the project on D: and inspect how the CLI resolves the config or user path. Done means the command no longer reports the ENOENT error, while still creating D:\Project\style-rtl.css with the expected defaults when no config is present.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.