Skip to content


npm logo

Npm is a package manager for JavaScript, included with Node.js. As a package manager, npm makes it easy for developers to share and reuse code.

Here are 13,906 public repositories matching this topic...

holmrenser commented Jan 6, 2022

I'm on a 14" macbook M1 pro and get the following error when trying to run a freshly downloaded/installed meteor 2.5.3:

Error: Only 64-bit Intel and M1 processors are supported on OS X

From the blogpost announcing meteor 2.5.1 I would expect meteor to work on my machine.
Given that I'm on an M1, the er

confirmed Impact:few good first issue Project:Apple
sabrinaluo commented Jun 5, 2019

Do you want to request a feature or report a bug?
feature request

What is the current behavior?
Currently yarn why won't indicate any package info in the resolutions field

If the current behavior is a bug, please provide the steps to reproduce.

  1. install a package with any version, e.g "pkg": "^1.0.0"
  2. add resolutions field in package.json, pkg: "1.0.0"
  3. upd
juanpicado commented Apr 19, 2022

Ìt seems a library is not compatible, needs further investigation, worth look into it.

packages/plugins/memory test: FAIL test/memory.spec.ts (9.385 s)
packages/plugins/memory test:   ● writing files › should abort while write a tarball
packages/plugins/memory test:     TypeError: Cannot set property closed of [object Object] which has only a getter
packages/plugins/memory test:       at 
marciel-truesoft commented Nov 19, 2020

Current Behavior

UMD build doesn't support code-splitting and dynamic imports (rollup/rollup#3490, rollup/rollup#3491) due to Rollup current limitations, and tsdx cli don't accept the format option amd when creating build config

Suggested Solution

Consider support AMD module format, o

kind: feature good first issue problem: stale PR welcome
zharinov commented May 10, 2022

Describe the proposed change(s).

It seems to be available starting from Node v17. See also:

type:refactor good first issue status:requirements priority-5-triage
Dionysusnu commented Dec 30, 2021

Hooks for scopes get a double prefix, ie @@scope, when shown with the npm hook ls command. This is due to the response from the web request already including the prefix in the name field, and the following lines of code then locally adding the prefix again, duplicating it.

Good First Issue Release 8.x Bug
matteobruni commented Apr 27, 2022

Version 2.x introduced a lot of new packages, almost every feature has a plugin package now but the component packages have some different versions and names.

Since I'd like to have the same version for the whole project, and a better naming, all packages, except "tsparticles" will be moved to the @tsparticles\ npm group.

This is what is going to be with version 3:


documentation enhancement help wanted good first issue
mtrunkat commented Sep 17, 2019

Main examples at Apify SDK webpage, Github repo and CLI templates should demonstrate how to manipulate with DOM and retrieve data from it.

Also add one example of scraping with Apify SDK + jQuery to

Feedback from:

I lost an hour trying to make

Created by Isaac Z. Schlueter

Released January 12, 2010