npm

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

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

I have a project that is in a monorepo and uses yarn right now.

I'm considering migrating to pnpm for the monorepo, as well as all other projects I contribute to, as I have a small SSD as local storage (and with Windows...). However, it would be ideal if there was compatibility between yarn's workspaces and pnpm, so that we don't have to jump "all in" to it.

To this end, yarn allows packages

Currently, path.join has a failing test:

These tests are taken from Node, so it likely is a real bug

The code implementing path.join is in this file: https://github.com/Jarred-Sumner/bun/blob/701d6ec45d7e339b352b37869bd2a7d4849b35fb/src/resolver/resolve

Your Environment
Not applicable. The issue is related to documentation.

Describe the bug

The Google Cloud documentation is non existent, even worse it displays jibberish.

• Markdown File: https://github.com/verdaccio/verdaccio/blob/master/website/docs/google-cloud.md
• Docs Site Link: https://verdaccio.org/docs/google-cloud/

To Reproduce

1. Visit [Docs > Google Cloud](ht

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

Describe the proposed change(s).

It seems to be available starting from Node v17. See also:
https://developer.mozilla.org/en-US/docs/Web/API/structuredClone

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.

What rule do you want to change?
vue/no-restricted-class

**Does this change cause th

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:

`tsparticles-engine

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 https://sdk.apify.com/docs/examples/basiccrawler

Feedback from: https://medium.com/better-programming/do-i-need-python-scrapy-to-build-a-web-scraper-7cc7cac2081d

I lost an hour trying to make