Greenstand/treetracker-query-api

vscode accidentally being able to tolerant wrong import path

Open

#41 opened on Jan 12, 2022

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)TypeScript (65 forks)auto 404
buggood first issuevscode

Repository metrics

Stars
 (17 stars)
PR merge metrics
 (PR metrics pending)

Description

If the relative path to import a module is wrong, VSCode still is able to find the file, but this makes trouble when we deploy the repo. on the cloud server, the node.js process throws error saying can not find the module.

Some hints:

  • Please read our readme for more information/guide/tutorial.
  • Here is an engineering book in Greenstand.
  • To know more about our organization, visit our website.
  • If you want to join the slack community (some resources need the community member's permission), please leave your email address.

Contributor guide

Research direction
Locate the incorrect import path in the source files. Compare the import path in VSCode with the actual file structure. Correct the path so that it resolves correctly in production.
Tech stack
typescriptnodejs
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.jsTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70