Скачать или смотреть Resolving the yarn workspaces Empty Folder Issue with Local Dependencies

Discover common problems with `yarn workspaces` and learn how to effectively resolve the empty folder issue for local dependencies in your Node.js projects.
---
This video is based on the question https://stackoverflow.com/q/77307005/ asked by the user 'The Blind Hawk' ( https://stackoverflow.com/u/16306754/ ) and on the answer https://stackoverflow.com/a/77342353/ provided by the user 'The Blind Hawk' ( https://stackoverflow.com/u/16306754/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: yarn workspaces adds empty folder instead of local dependency

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Issue with Yarn Workspaces

When working with yarn workspaces, a powerful tool for managing monorepos in Node.js, you might encounter frustrating issues such as an empty folder being created instead of properly linking local dependencies. This can be particularly distressing when you're trying to integrate different packages for a project that utilizes both front-end and back-end functionality.

In this guide, we'll delve into one such problem reported by developers using Yarn on a Windows 11 system with WSL 2. Specifically, we'll look at the case where attempting to add local dependencies results in the creation of an empty folder. We will explore the symptoms, probable causes, and practical solutions to this problem.

The Background: Setup and Structure

Let's set the stage with a basic understanding of the setup. The developer in question has a directory structured as follows:

[[See Video to Reveal this Text or Code Snippet]]

Package Configuration

The developer's root package.json resembles:

[[See Video to Reveal this Text or Code Snippet]]

The configurations for both the front-end and back-end are set up correctly, allowing for shared access to common modules.

The Expected vs. Actual Behavior

When attempting to add the backend as a dependency for the frontend with the command:

[[See Video to Reveal this Text or Code Snippet]]

Expected Outcomes

A folder named @ project/backend should appear in the frontend's node_modules.

The backend types should be accessible in the frontend with proper import statements.

The command should execute without any errors.

Actual Outcomes

An empty folder titled @ project is created inside the frontend's node_modules.

There are issues with accessing backend types using import statements.

No error messages are generated during the execution of the command.

Diagnosing the Problem

From the description of the problem, it appears that the core issue resides in how Yarn interacts with WSL (Windows Subsystem for Linux). Here are some key observations:

Running yarn install within WSL leads to the persistent presence of empty local node_modules folders.

Attempting to re-run the install command from PowerShell does not resolve the issue unless the yarn.lock file and node_modules are deleted first.

Testing the same configuration on MacOS did not yield the same issues, suggesting that the problem could be specific to the Windows and WSL environment.

Solutions to Consider

1. Delete and Reinstall

As a workaround, consider the following steps:

Remove the yarn.lock file and node_modules folder in both the root and affected package directories.

Run yarn install from PowerShell instead of WSL. This could help reconstruct your local dependencies correctly.

2. Using WSL Cautiously

If you intend to work within WSL:

Be aware that the adaptations of Yarn in WSL might differ from how it operates on native Unix systems.

Monitor Yarn updates and documentation for any changes regarding compatibility with WSL functionalities.

3. Deployment Considerations

Interestingly, even with the empty node_modules, the developer found that they could still deploy the server locally by running yarn run dev. This highlights the complexity of the situation, where some commands may bypass the need for complete dependency installations despite import issues.

Conclusion

Resolving the empty folder issue with yarn workspaces on WSL can be tricky, but understanding the behaviors and interactions of different environments can pave the way for solutions. Deleting the lock file and ensuring installs are performed in the right environment can often mitigate these challenges.

If you encounter this issue, try out the