Skip to content

Commit c776aa0

Browse files
committed
Merge branch 'installation-issues' into develop
2 parents a9b8973 + 8c1d119 commit c776aa0

File tree

2 files changed

+11
-0
lines changed

2 files changed

+11
-0
lines changed

.gitattributes

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1 +1,3 @@
11
package-lock.json -diff
2+
* text=auto
3+
*.sh text eol=lf

docs/FAQ.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,3 +41,12 @@ which should output something similar to `arm64`. Then, `npm i @tensorflow/tfjs`
4141
### VSCode can't resolve imports
4242

4343
You may not be able to open the editor from the repo root level without VSCode raising imports errors. If that is the case, you should start VSCode from inside the module you are working such that the editor can resolve the imports. In practice, that is any folder level that contains a package.json such as `server`, `webapp`, etc. For example, if you are working on the CLI, you should start VSCode with the command `code cli` from the root level (or `cd cli`, `code .`)
44+
45+
### npm failing to download or install packages
46+
47+
Firewall settings can sometimes block npm's network requests, preventing it from downloading packages.
48+
49+
**Troubleshooting:**
50+
1. Temporarily disable the firewall. If npm works, the firewall is the cause.
51+
2. Identify the specific firewall rule that is blocking npm and adjust it.
52+
3. Make sure your firewall allows outbound HTTPS (port 443) connections to `registry.npmjs.org`.

0 commit comments

Comments
 (0)