angular/angular-cli

Running ng commands when project is stored on shared/symlinked network drive

Open

#11948 opened on Aug 20, 2018

View on GitHub
 (5 comments) (2 reactions) (0 assignees)TypeScript (26,585 stars) (11,999 forks)batch import
area: etc/miscfreq1: lowhelp wantedseverity3: brokentype: bug/fix

Description

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)

- [ ] new
- [x] build
- [x] serve
- [x] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [x] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

node -v v8.11.3

npm --version 6.3.0

ng --version Angular CLI: 6.1.3 Node: 8.11.3 OS: win32 x64 Angular: 5.2.11 ... animations, common, compiler, compiler-cli, core, forms ... http, language-service, platform-browser ... platform-browser-dynamic, router

Package Version ----------------------------------------------------------- @angular-devkit/architect 0.6.8 @angular-devkit/build-angular 0.6.8 @angular-devkit/build-optimizer 0.6.8 @angular-devkit/core 0.6.8 @angular-devkit/schematics 0.7.3 @angular/cli 6.1.3 @ngtools/webpack 6.0.8 @schematics/angular 0.7.3 @schematics/update 0.7.3 rxjs 5.5.11 typescript 2.5.3 webpack 4.8.3

Repro steps

Have a directory mapped to network drive. When ng command is run the directory path is resolved with ip of network drive so instead C:\Projects\AITeF\AITeF it is resolved to : C:\192.168.*.*\Projects_D2\AITeF\AITeF

The log given by the failure

image

Desired functionality

Mention any other details that might be useful

I moved my project to remote desktop on Windows 10. The local drive that project is on is symlinked to a network drive so all computers in my company have access to it. Unfortunately, when things are configured this way, I cannot run any ng command. They always give an error like this.

It's because it tries to acces the project via 'C:\192.168..\Projects_D2\AITeF\AITeF while the path should look like this C:\Projects\AITeF\AITeF.

I tried adding "preserveSymlinks": true in my angular.json file but this doesn't work.

Contributor guide

Tech stack
typescriptnodejs
Domain
clibuild systemtooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptNode.js path moduleAngular CLI internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
The issue involves path resolution when the project is on a symlinked network drive. Investigate how Angular CLI resolves the project root path, likely in @angular devkit/core or architect. Look for usage of `fs.realpathSync` or similar. Check if the `preserveSymlinks` option in angular.json is properly passed to Node.js module resolution. Consider using `fs.realpathSync.native` to resolve symlinks before using the path. Review any related PRs or comments for prior attempts.