[Languages] - Typescript Playground

Open
#537 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
node.js, typescript
Domain
tooling

Research direction

Start by locating the Typescript Playground package.json and read its current project metadata. Add the requested Node and npm engine constraints, then verify that the package configuration reflects the versions described in the issue and that the project can be executed with a compatible Node version.

Written by the indexing model from the issue text.

Description

In the package.json should be the engine attribute, since the developers that have more projects with multi node engine can have errors when executing the project.

The example is typescript with top version 5 and node engine 12 (it is possible to have projects with this version still), when executing the project it would not transpile because it is not compatible with this version.

I think it is the best practice to add to the package version engine attribute like this:

{
  "engines": {
    "node": ">=16.0.0",
    "npm": ">=6.0.0"
  }
}
Dominant language
TypeScript
Stars
184
Forks
99
Avg merge
1m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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 Lemoncode/master-frontend-lemoncode

All issues in Lemoncode/master-frontend-lemoncode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.