swc_common and serde Dependency Error when installing red on windows

[BaderNader321]

Error:

Compiling swc_common v9.2.0
error[E0432]: unresolved import serde::__private
--> C:\Users\arifa.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\swc_common-9.2.0\src\private\mod.rs:3:9
|
3 | pub use serde::__private as serde;
| ^^^^^^^---------^^^^^^^^^
| | |
| | help: a similar name exists in the module: private
| no __private in the root

Compiling minimal-lexical v0.2.1
Compiling crc32fast v1.5.0
Compiling nom v7.1.3
Compiling par-iter v1.0.2
For more information about this error, try rustc --explain E0432.
error: could not compile swc_common (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: failed to compile red v0.1.0 (C:\Users\arifa\red), intermediate artifacts can be found at C:\Users\arifa\red\target.
To reuse those artifacts with a future compilation, set the environment variable CARGO_TARGET_DIR to that path.

---

I ran "rustc --explain E0432" and the results is:
red on  master is 󰏗 v0.1.0 via 󱘗 v1.91.0 took 18m24s
✦ ❯ rustc --explain E0432
An import was unresolved.

Erroneous code example:

use something::Foo; // error: unresolved import `something::Foo`.

In Rust 2015, paths in use statements are relative to the crate root. To
import items relative to the current and parent modules, use the self:: and
super:: prefixes, respectively.

In Rust 2018 or later, paths in use statements are relative to the current
module unless they begin with the name of a crate or a literal crate::, in
which case they start from the crate root. As in Rust 2015 code, the self::
and super:: prefixes refer to the current and parent modules respectively.

Also verify that you didn't misspell the import name and that the import exists
in the module from where you tried to import it. Example:

use self::something::Foo; // Ok.

mod something {
    pub struct Foo;
}

If you tried to use a module from an external crate and are using Rust 2015,
you may have missed the extern crate declaration (which is usually placed in
the crate root):

extern crate core; // Required to use the `core` crate in Rust 2015.

use core::any;

Since Rust 2018 the extern crate declaration is not required and
you can instead just use it:

use core::any; // No extern crate required in Rust 2018.