Missing en.json File Error When Running Fleek CLI

[DruxAMB]

Bug Description:

After installing the Fleek CLI globally using npm, I attempted to check the version using the fleek version command, but I encountered an error related to a missing en.json file.

Error Message:

Error: ENOENT: no such file or directory, open 'C:\Users\HP Elitebook Mt44\AppData\Roaming\npm\node_modules@fleek-platform\cli\dist\locales\en.json' at readFileSync (node:fs:448:20) at loadJSONFromPackageRoot (C:\Users\HP Elitebook Mt44\AppData\Roaming\npm\node_modules@fleek-platform\cli\dist\bundle.js:105957:53)

Steps to Reproduce:

1. Run npm install -g @fleek-platform/cli
2. Run fleek version
3. See the error

Expected Behavior:

The command fleek version should display the version number without throwing an error.

System Information:

• Node.js Version: v20.17.0
• NPM Version: v10.8.3
• Operating System: Windows 10
• Fleek CLI Version: The latest version from npm

Additional Context:

I also received warnings about deprecated packages during installation:
npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. npm WARN deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported.

Please let me know if any additional information is needed.

[KanishkKhurana]

Since you are running the CLI on a windows machine, could you specify which command line tool was used to install the CLI ?
Please also try running powershell as administrator and then installing or using WSL

[DruxAMB]

I used the command provided on fleek CLI, like fleek version, fleek. All commands starting with fleek throw the same error. I have also tried running as administrator but throws the same error message. That means the command line only works in a Linux environment?

…

On Thu, Sep 26, 2024 at 9:57 AM Kanishk Khurana ***@***.***> wrote: Since you are running the CLI on a windows machine, could you specify which command line tool was used to install the CLI ? Please also try running powershell as administrator and then installing or using WSL — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7FAUH4ADGDVVUPBUSJIQBDZYPEADAVCNFSM6AAAAABOUE344GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGM2TSMZVG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[adharshchottu]

the file doesn't exists in the package? so regardless of environment it will ended in error?

[fleekgonzalo]

I used the command provided on fleek CLI, like fleek version, fleek. All commands starting with fleek throw the same error. I have also tried running as administrator but throws the same error message. That means the command line only works in a Linux environment?
…
On Thu, Sep 26, 2024 at 9:57 AM Kanishk Khurana @.> wrote: Since you are running the CLI on a windows machine, could you specify which command line tool was used to install the CLI ? Please also try running powershell as administrator and then installing or using WSL — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7FAUH4ADGDVVUPBUSJIQBDZYPEADAVCNFSM6AAAAABOUE344GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGM2TSMZVG4 . You are receiving this because you authored the thread.Message ID: @.>

Yes, at the moment you need a linux environment to run fleek cli. That means you should use WSL or similar on windows.

[levalleux-ludo]

Hi @fleekgonzalo
Any chance you could add a warning in your documentation, telling that "at the moment you need a linux environment to run fleek cli. That means you should use WSL or similar on windows" ?
That would be great! Thanks

[KarbitsCode]

Hi everyone, I found the problem.
It turns out it's just because the Linux directory slash ("/") is being hardcoded in the code, specifically in src/utils/json.ts:

cli/src/utils/json.ts

Lines 6 to 14 in 342f217

	// The build distribution target directory
	const BUILD_DIST_PATHNAME = '/dist';
	// Fallback path is the `src` used in tests
	const TEST_SRC_PATHNAME = '/src';
	const leadingSlash = (str: string) => (str.startsWith('/') ? str : `/${str}`);
	const resolvePath = (filename: string) => {

Since in Windows, they use "\" for path separation.
So, the fix is just to use the path.sep constant for path separation instead of hardcoding the "/", like this:

index ffa8fff..e41c6fb 100644
--- a/node_modules/@fleek-platform/cli/src/utils/json.ts
+++ b/node_modules/@fleek-platform/cli/src/utils/json.ts
@@ -4,12 +4,12 @@ import { readFileSync } from 'node:fs';
 import path from 'node:path';
 
 // The build distribution target directory
-const BUILD_DIST_PATHNAME = '/dist';
+const BUILD_DIST_PATHNAME = path.sep + 'dist';
 
 // Fallback path is the `src` used in tests
-const TEST_SRC_PATHNAME = '/src';
+const TEST_SRC_PATHNAME = path.sep + 'src';
 
-const leadingSlash = (str: string) => (str.startsWith('/') ? str : `/${str}`);
+const leadingSlash = (str: string) => (str.startsWith(path.sep) ? str : `${path.sep}${str}`);
 
 const resolvePath = (filename: string) => {

I did confirm now it works perfectly in Windows environment without WSL. Let me know if you guys have any questions about this.

[SpriteDay]

@KarbitsCode's solution is working perfectly, can anyone from the team push this update with path.sep please? This issue goes here for way too long guys, a lot of devs use Windows and not even having a warning in package documentation is a shame, when people already found a solution and you just have to push it

[Teerchh]

Hi everyone, I found the problem. It turns out it's just because the Linux directory slash ("/") is being hardcoded in the code, specifically in src/utils/json.ts:

cli/src/utils/json.ts

Lines 6 to 14 in 342f217

// The build distribution target directory
const BUILD_DIST_PATHNAME = '/dist';

// Fallback path is the src used in tests
const TEST_SRC_PATHNAME = '/src';

const leadingSlash = (str: string) => (str.startsWith('/') ? str : /${str});

const resolvePath = (filename: string) => {
Since in Windows, they use "" for path separation. So, the fix is just to use the path.sep constant for path separation instead of hardcoding the "/", like this:

index ffa8fff..e41c6fb 100644
--- a/node_modules/@fleek-platform/cli/src/utils/json.ts
+++ b/node_modules/@fleek-platform/cli/src/utils/json.ts
@@ -4,12 +4,12 @@ import { readFileSync } from 'node:fs';
import path from 'node:path';

// The build distribution target directory
-const BUILD_DIST_PATHNAME = '/dist';
+const BUILD_DIST_PATHNAME = path.sep + 'dist';

// Fallback path is the src used in tests
-const TEST_SRC_PATHNAME = '/src';
+const TEST_SRC_PATHNAME = path.sep + 'src';

-const leadingSlash = (str: string) => (str.startsWith('/') ? str : /${str});
+const leadingSlash = (str: string) => (str.startsWith(path.sep) ? str : ${path.sep}${str});

const resolvePath = (filename: string) => {
I did confirm now it works perfectly in Windows environment without WSL. Let me know if you guys have any questions about this.

tried this still didn't work help please