chatie / tsconfig Goto Github PK

4.5.3一直到最新版本均有此问题，导致整个项目npm i 失败

npm WARN deprecated [email protected]: 16.1.1
npm ERR! code 1
npm ERR! path C:\Users\Administrator\Documents\GitHub\chatflow\node_modules\node-jq
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c npm run install-binary
npm ERR! > [email protected] install-binary
npm ERR! > node scripts/install-binary.js
npm ERR!
npm ERR! Downloading jq from https://github.com/stedolan/jq/releases/download/jq-1.6/jq-win64.exe
npm ERR! GotError [RequestError]: connect ETIMEDOUT 20.205.243.166:443
npm ERR! at ClientRequest. (C:\Users\Administrator\Documents\GitHub\chatflow\node_modules\got\index.js:182:22)
npm ERR! at Object.onceWrapper (node:events:642:26)
npm ERR! at ClientRequest.emit (node:events:527:28)
npm ERR! at TLSSocket.socketErrorListener (node:_http_client:454:9)
npm ERR! at TLSSocket.emit (node:events:527:28)
npm ERR! at emitErrorNT (node:internal/streams/destroy:157:8)
npm ERR! at emitErrorCloseNT (node:internal/streams/destroy:122:3)
npm ERR! at processTicksAndRejections (node:internal/process/task_queues:83:21) {
npm ERR! code: 'ETIMEDOUT',
npm ERR! host: 'github.com',
npm ERR! hostname: 'github.com',
npm ERR! method: 'GET',
npm ERR! path: '/stedolan/jq/releases/download/jq-1.6/jq-win64.exe',
npm ERR! protocol: 'https:',
npm ERR! url: 'https://github.com/stedolan/jq/releases/download/jq-1.6/jq-win64.exe'
npm ERR! }

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Local\npm-cache_logs\2024-01-25T18_49_45_701Z-debug-0.log

It's strange that the following error message appears from the GitHub Actions log yesterday.

I retried serval times but this error persists for a while.

However, it seems it's gone today, so I guess it's a bug related to GitHub Actions system.

> cross-env NODE_OPTIONS="--no-warnings --loader=ts-node/esm" tap "src/**/*.spec.ts" "tests/**/*.spec.ts"

TAP version 13
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /home/runner/work/puppet/puppet/src/busy-indicator.spec.ts
    at new NodeError (node:internal/errors:371:5)
    at Object.file: (node:internal/modules/esm/get_format:72:15)
    at defaultGetFormat (node:internal/modules/esm/get_format:85:38)
    at defaultLoad (node:internal/modules/esm/load:13:42)
    at ESMLoader.load (node:internal/modules/esm/loader:303:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:230:58)
    at new ModuleJob (node:internal/modules/esm/module_job:63:26)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:244:11)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:281:24) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}

See:

• Why does typescript allow me to import dependencies it can't use at runtime?

Solution

npm install --save uuid
npm install --save-dev @types/uuid

and

import * as UUID from 'uuid'

See my SO answer

Progress

• Wechaty Getting Started
• Wechaty
• WechatyPuppet
• WechatyGrpc
• Helper modules
  • StateSwitch
  • FileBox
  • tstest
  • HotImport
  • CloneClass
  • MemoryCard
  • WatchDog
  • FlashStore
  • Brolog
  • RxQueue
  • Finis
  • AsyncMapLike
  • Ducks
• Puppets
  • PuppetWeChat
  • PuppetWeChat4U
  • PuppetWhatsapp
  • PuppetPadlocal
  • PuppetXp
  • PuppetGitter
  • PuppetLark
  • PuppetDonut
  • PuppetWXWork
  • PuppetOfficialAccount
  • PuppetMock
  • PuppetService
  • PuppetOICQ
• Ecosystem
  • HA Wechaty
  • Wechaty Mocker
  • CLI
  • Wechaty Plugin Contrib
  • Wechaty Redux
  • Wechaty Vorpal
  • Wechaty Vorpal Contrib
  • Wechaty Official Website
  • Matrix AppService Wechaty
  • Wechaty Ducks Contrib
  • WechatyChatOpera
  • Wechaty QnAMaker
  • Wechaty Token
• Wechaty BOTs
  • OSS.Chat BOT
  • Friday BOT

Howto

• Node Modules at War: Why CommonJS and ES Modules Can’t Get Along
• How to Create a Hybrid NPM Module for ESM and CommonJS.
• The ESM move #15
• Publishing Node modules with TypeScript and ES modules

Links

• Get Ready For ESM, Sindre Sorhus, Jan 13, 2021
• TypeStrong/ts-node#1007
• TypeStrong/ts-node#935
• Pure ESM Package
• CommonJS to ESM in Node.js
• Hybrid npm packages (ESM and CommonJS)
• Aaaaaaaaaaaaaah, They’re Here! ES Modules in Node.JS - Gil Tayar | Node.TLV 2020
• Joshua's Docs - Building an NPM Package - Notes, Tips, and Troubleshooting
• TypeScript and native ESM on Node.js

Badge

[![ES Modules](https://img.shields.io/badge/ES-Modules-brightgreen)](https://github.com/Chatie/tsconfig/issues/16)

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Add a unit test for making sure that the tsconfig.json work without any problem after packing.