Alexander Kachkaev
Alexander Kachkaev
`[email protected]` could solve the problem indeed, but it would require this module to become ESM-only. See - https://github.com/sindresorhus/read-pkg/releases/tag/v6.0.0 - https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c Using `[email protected]` still gives us a vulnerable version of `hosted-git-info`....
An attempt to fix the issue is here: https://github.com/mysticatea/npm-run-all/pull/205 I have some issues with AppVeyor and am giving up for now. Any help would be appreciated! @mysticatea 🙏
@dtothefp which alternative have you been able to find?
Not sure what’s wrong, but I’m seeing this in AppVeyor: ``` > [email protected] _mocha C:\projects\npm-run-all > mocha "test/*.js" --timeout 120000 internal/modules/cjs/loader.js:818 throw err; ^ Error: Cannot find module 'C:\projects\npm-run-all\node' at...
👋 @mysticatea what are your thoughts on the failing AppVeyor?
@mysticatea 👋🙏
@mysticatea 👋😅
This worked for me in a ESM file: ```js import { foo } from "foo"; import { bar } from "./path/to/bar"; (await import("dotenv-flow")).config(); console.log(process.env.HELLO); ``` Because static imports are async...
Thanks for sharing your workaround folks! Here's my solution for a microservice on node 10: ```dockerfile FROM node:10.15.1-alpine RUN mkdir -p /app/ WORKDIR /app/ COPY package.json yarn.lock /app/ ## https://github.com/nodegit/nodegit/issues/1361...
@pedronauck what are your thoughts? Seems like there is quite some interest in this problem, according to the number of 👍 🙂