remove upstream scripts

Open
#1,457 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
cli

Research direction

Start by tracing the CLI installation path and the package scripts associated with the two upstream packages named in the warning. Done means installing the CLI no longer produces the reported allow-scripts messages; the issue does not name a file or test, so confirm the expected installation output with the maintainers.

Written by the indexing model from the issue text.

Description

to avoid these messages when installing CLI:

added 205 packages in 5s

39 packages are looking for funding
  run `npm fund` for details
npm warn allow-scripts 2 packages have install scripts not yet covered by allowScripts:
npm warn allow-scripts   @sasjs/lint@2.4.3 (preinstall: node checkNodeVersion)
npm warn allow-scripts   @sasjs/utils@3.5.2 (preinstall: npm run nodeVersionMessage)
npm warn allow-scripts
npm warn allow-scripts Run `npm install -g --allow-scripts=@sasjs/lint,@sasjs/utils` to allow these scripts once, or `npm config set allow-scripts=@sasjs/lint,@sasjs/utils --location=user` to allow them for all global installs.
Dominant language
TypeScript
Stars
40
Forks
6
Avg merge
1d 16h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

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 sasjs/cli

All issues in sasjs/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.