deep-foundation / deep-foundation/npm-packager

No requests should be done to NPM in case `packageClientHandler` is opened for the first time or package name is empty

Open
#68 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
8
Forks
1
PR merge metrics
No merged PRs in 30d

Description

![Screenshot_20230928_201850](https://github.com/deep-foundation/npm-packager/assets/1431904/0941231e-60ad-464c-9bc5-58062ec0072e)

```
Access to XMLHttpRequest at 'https://registry.npmjs.com/' from origin 'https://deep.deep.foundation' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
4294-411eddb750d032e1.js:310 GET https://registry.npmjs.com/ net::ERR_FAILED 200
```

# Workaround

Ignore the error.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the packageClientHandler entry point and reproduce the case by opening it for the first time and by leaving the package name empty. Verify in the browser network log that neither case sends a request to registry.npmjs.com; done means the CORS-producing request no longer occurs in both scenarios.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.