profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Eomm/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Manuel Spigolon Eomm @nearform Italy If you need it, implement it. I mean: your skills ๐Ÿฑโ€๐Ÿ

Eomm/digi-tags 9

A collection of knowledge resources for IT enthusiast!

Eomm/choose-it 2

Choose a resource in a Jungle ๐ŸŒด๐ŸŒด๐ŸŒด tree

Eomm/alexa-github-stars 1

A skill for Alexa to interacts with GitHub!

Eomm/autocannon 1

fast HTTP/1.1 benchmarking tool written in Node.js

Eomm/avvio 1

Asynchronous bootstrapping of Node applications

Eomm/bull 1

Premium Queue package for handling distributed jobs and messages in NodeJS.

Eomm/cli 1

a package manager for JavaScript, report bugs and get support at:

Eomm/commist 1

Build your commands on minimist!

Eomm/convert-units 1

An elegant way to convert quantities between different units.

Eomm/dolm 1

Document Lifecycle Management is a maven plugin for managing documentation across developers and manager using markdown. The software developer's team can create and update the documentation using his VCS and build a nice PDF (for now) for the customers or the top management that don't know what is it markdown.

issue openednpm/cli

[BUG] npm stuck during workspace installation

Is there an existing issue for this?

  • [X] I have searched the existing issues

Current Behavior

Running the installation of modules that has a mismatch peerDependancy lead to an infinite installation within the process stuck at 100% CPU

image

The origin of this issue comes from solving the installation issue on this project, where I used --legacy-peer-deps to complete the installation: https://github.com/nearform/titus/runs/3967425473?check_suite_focus=true

titus@1.0.0 /Users/mspigolon/workspace/titus
โ”œโ”€โ”ฌ titus-backend@1.0.0-alpha.1 -> ./packages/titus-backend
โ”‚ โ””โ”€โ”ฌ @nearform/brokeneck-fastify@1.0.0-spinal.8
โ”‚   โ””โ”€โ”ฌ @nearform/brokeneck-html@1.0.0-spinal.8
โ”‚     โ””โ”€โ”ฌ react-scripts@4.0.1
โ”‚       โ””โ”€โ”€ babel-loader@8.1.0
โ””โ”€โ”ฌ titus-frontend@1.0.0-alpha.1 -> ./packages/titus-frontend
  โ”œโ”€โ”ฌ @storybook/addon-docs@6.3.12
  โ”‚ โ”œโ”€โ”ฌ @storybook/builder-webpack4@6.3.12
  โ”‚ โ”‚ โ””โ”€โ”€ babel-loader@8.2.3
  โ”‚ โ””โ”€โ”ฌ @storybook/core@6.3.12
  โ”‚   โ””โ”€โ”ฌ @storybook/core-server@6.3.12
  โ”‚     โ””โ”€โ”ฌ @storybook/manager-webpack4@6.3.12
  โ”‚       โ””โ”€โ”€ babel-loader@8.2.3 deduped
  โ”œโ”€โ”ฌ @storybook/react@6.3.12
  โ”‚ โ””โ”€โ”ฌ @storybook/core-common@6.3.12
  โ”‚   โ””โ”€โ”€ babel-loader@8.2.3 deduped
  โ””โ”€โ”ฌ react-scripts@4.0.3
    โ””โ”€โ”€ babel-loader@8.1.0

The titus-frontend loads:

/titus/node_modules/babel-loader

instead of:

/titus/node_modules/react-scripts/node_modules/babel-loader

Maybe it is related to: https://github.com/npm/cli/issues/3208

Expected Behavior

The installation should complete

Steps To Reproduce

mkdir npm-stuck
cd npm-stuck
npm init --yes
npm init -w pkg-a --yes
npm install react-scripts -w pkg-a
npm install @storybook/react -D -w pkg-a

Environment

Github action (all OSs and npm 8.1.0 and 7.24.2) https://github.com/Eomm/npm-stuck/actions/runs/1371673160

Note the windows jobs are green, but it shows the out of memory stacktrace.

created time in 15 hours

push eventEomm/npm-stuck

Manuel Spigolon

commit sha 9314b54c93e3b097d81c0e03e105f1dbe4157d5b

conditional step

view details

push time in 16 hours

push eventEomm/npm-stuck

Manuel Spigolon

commit sha e8cbbb13a7afc3a0fb4fd71d7da0c628ee6c1299

check npm stuck

view details

push time in 16 hours

create barnchEomm/npm-stuck

branch : main

created branch time in 16 hours

created repositoryEomm/npm-stuck

created time in 16 hours

create barnchnearform/titus

branch : npm-workspaces

created branch time in a day

issue commentnpm/rfcs

[RRFC] npm run-series && npm run-parallel

This feature could be adapted to be used on workspaces too.

npm run-parallel lint --workspaces

executes in parallel the lint script for each project in the monorepo.

MylesBorins

comment created time in a day

issue closednpm/cli

[Feature] npm workspaces --parallel

There are some scripts on a monorepo that can run in parallel to speed up the command execution.

It would be useful to integrate the --parallel flag as implemented in lerna.

example:

npm run lint --parallel --workspaces

runs the echo script for each project workspace.

The result would be:

  • successful if all the commands are completed successfully
  • or fail if once returns an error

closed time in a day

Eomm

issue commentnpm/cli

[Feature] npm workspaces --parallel

Yes, I found this issue on that repo: https://github.com/npm/rfcs/issues/190 that fits a bit

I will continue the discussion there

Thanks

Eomm

comment created time in a day

issue commentFormidableLabs/pino-lambda

Expose this library as a pino mixin

I think we could find a good balance to do it using the default Pino apis.

Here is a quick&dirty example using:

  • pino mixin
  • within pino destination https://github.com/pinojs/pino/blob/master/docs/api.md#destination

The pino transport would be the best fit (the JSON.parse can be skipped), but I don't know if it works as expected on the Lambda environment

'use strict'

const pino = require('pino')
const { Transform, Writable } = require('stream')

const cloudwatchWritable = new Writable({
  defaultEncoding: 'utf8',
  write(chunk, encoding, callback) {
    const obj = JSON.parse(chunk)
    const time = new Date().toISOString();
    console.log(`${time}\t${obj.awsRequestId}\t${obj.msg}`)
    callback()
  }
})

let n = 0
const logger = pino({
  mixin() {
    return { awsRequestId: ++n }
  }
}, cloudwatchWritable)
logger.info('hello')
// 2021-10-21T16:46:49.985Z        1       hello

simoneb

comment created time in a day

issue openednpm/cli

[Feature] npm workspaces --parallel

There are some scripts on a monorepo that can run in parallel to speed up the command execution.

It would be useful to integrate the --parallel flag as implemented in lerna.

example:

npm run lint --parallel --workspaces

runs the echo script for each project workspace.

The result would be:

  • successful if all the commands are completed successfully
  • or fail if once returns an error

created time in a day

push eventnearform/the-fastify-workshop

Manuel Spigolon

commit sha 066ab1d70313488ce4a682fc770478ca7c0d3288

Npm workspaces (#172) * migrate to npm workspaces * update ci * clean project * fix per suggestion * chore: fix readme * audit fix * chore: fix readme * typo

view details

push time in a day

delete branch nearform/the-fastify-workshop

delete branch : npm-workspaces

delete time in a day

PR merged nearform/the-fastify-workshop

Npm workspaces

Closes #24

Setting node 16 on CI since it will become LTS in 5 days (26th October) Or we need to execute npm install -g npm@latest

+13810 -4167

2 comments

20 changed files

Eomm

pr closed time in a day

issue closednearform/the-fastify-workshop

npm v7 support vs yarn?

As titled

closed time in a day

mcollina

push eventnearform/the-fastify-workshop

Manuel Spigolon

commit sha a3e258d13bbd19c92e7d6130ce170790fac16091

typo

view details

push time in a day

push eventnearform/the-fastify-workshop

Manuel Spigolon

commit sha 31540b6983081bab59a563a8bfb7dbd9aa867d91

chore: fix readme

view details

push time in a day

pull request commentnearform/the-fastify-workshop

Npm workspaces

@simoneb do you know how to check the snyk failing stage? It blocks me from viewing the details

Eomm

comment created time in a day

push eventnearform/the-fastify-workshop

Manuel Spigolon

commit sha 16ab94c73108bfecac9ea3e2d6f6c1c345502487

audit fix

view details

push time in a day

Pull request review commentnearform/the-fastify-workshop

Npm workspaces

+if-present = true

No, but the command was running the root's test command that navigates the project's tree and executes all the .test.js files.

The right command to execute in this case should be yarn workspaces run test https://classic.yarnpkg.com/en/docs/cli/workspaces#toc-yarn-workspaces-run

Eomm

comment created time in a day

PullRequestReviewEvent

push eventnearform/the-fastify-workshop

Manuel Spigolon

commit sha 1055ffeb2786f79ff1e112b4e7091339df5525db

chore: fix readme

view details

push time in a day

Pull request review commentnearform/the-fastify-workshop

Npm workspaces

+if-present = true

Some steps do have not the test script, so npm would fail to run the npm test on those steps.

With that flag, npm will ignore those projects/steps that do not have the test script. The file is useful to avoid writing it on the command line executed by the user

Details here: https://docs.npmjs.com/cli/v7/using-npm/config#if-present

Eomm

comment created time in a day

PullRequestReviewEvent

push eventnearform/the-fastify-workshop

dependabot[bot]

commit sha 548a31dade2a76ea4984e4e1ba9857796ebb2d01

build(deps): bump fastify from 3.22.0 to 3.22.1 (#167) Bumps [fastify](https://github.com/fastify/fastify) from 3.22.0 to 3.22.1. - [Release notes](https://github.com/fastify/fastify/releases) - [Commits](https://github.com/fastify/fastify/compare/v3.22.0...v3.22.1) --- updated-dependencies: - dependency-name: fastify dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

Matteo Collina

commit sha 54cf5b8c9ecb4b6830432e6802a1ddaac6e7efe1

Updated project stats

view details

Manuel Spigolon

commit sha 97b6856b6d841d88f0bc6ec364e1a39e219500ac

Merge remote-tracking branch 'origin/master' into npm-workspaces

view details

Manuel Spigolon

commit sha bc58406ca1f8262006d9b64cdfb9a3230a609d45

fix per suggestion

view details

push time in a day

PR opened nearform/the-fastify-workshop

Reviewers
Npm workspaces

Closes #24

Setting node 16 on CI since it will become LTS in 5 days (26th October) Or we need to execute npm install -g npm@latest

+13642 -4136

0 comment

7 changed files

pr created time in 2 days

push eventnearform/the-fastify-workshop

Manuel Spigolon

commit sha b920aff6b4beb24e304a6ad4a853198cfe10489d

clean project

view details

push time in 2 days

create barnchnearform/the-fastify-workshop

branch : npm-workspaces

created branch time in 2 days

issue openedMattiLehtinen/postgrator-cli

CLI Warnings

Hi

Running postgrator (cli) with the example postgrator.json

{
  "migrationDirectory": "migrations",
  "driver": "pg",
  "host": "127.0.0.1",
  "port": 5433,
  "database": "postgres",
  "username": "postgres",
  "password": "postgres"
}

Lead to this output

postgrator deprecated Config option "port". Implement execQuery function instead. node_modules/postgrator-cli/postgrator-cli.js:222:26
postgrator deprecated Config option "host". Implement execQuery function instead. node_modules/postgrator-cli/postgrator-cli.js:222:26
postgrator deprecated Config option "username". Implement execQuery function instead. node_modules/postgrator-cli/postgrator-cli.js:222:26
postgrator deprecated Config option "password". Implement execQuery function instead. node_modules/postgrator-cli/postgrator-cli.js:222:26
postgrator deprecated Config option "migrationDirectory". use "migrationPattern" instead using glob match. e.g. path.join(__dirname, '/migrations/*') node_modules/postgrator-cli/postgrator-cli.js:222:26

The postgrator version is 4.3.1

I saw that these warnings have been introduced in 4.3.0 https://github.com/rickbergfalk/postgrator/pull/131

created time in 2 days

push eventEomm/fastify-in-practice

Manuel Spigolon

commit sha f0f7560a12531527fae43d2d3494ce22e3a8678d

add shortcut

view details

push time in 2 days