validate http libs are present

Open
#63 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
nodejs, typescript
Domain
backend

Research direction

Read src/index.ts around lines 11 and 165 to understand the HTTP library imports and the referenced naming or replacement behavior. Clarify whether the intended outcome is a rename or a validation check, then verify that browser users receive an appropriate failure when the libraries are replaced or missing.

Written by the indexing model from the issue text.

Description

feature

i am really thinking about renaming this https://github.com/fent/node-miniget/blob/master/src/index.ts#L165

or adding a check after https://github.com/fent/node-miniget/blob/master/src/index.ts#L11

just to make sure that people don't screw up when replacing them e.g. when using in a browser

Dominant language
TypeScript
Stars
57
Forks
19
Avg merge
1d 23h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fent/node-miniget

All issues in fent/node-miniget

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.