vercel/pkg

package error with steam-user

feeops opened this issue · 2 comments

feeops commented

What version of pkg are you using?

5.8.1

What version of Node.js are you using?

20.3.1

What operating system are you using?

macOS

What CPU architecture are you using?

Apple M1

What Node versions, OSs and CPU architectures are you building for?

node18-win-x64

Describe the Bug

`pkg/prelude/bootstrap.js:1872
throw error;
^

Error: Cannot find module 'C:\snapshot\case_move\node_modules\lzma\src\lzma_worker.js'
Require stack:

  • C:\snapshot\case_move\node_modules\lzma\index.js
  • C:\snapshot\case_move\node_modules\steam-user\components\cdn.js
  • C:\snapshot\case_move\node_modules\steam-user\components\chat.js
  • C:\snapshot\case_move\node_modules\steam-user\components\econ.js
  • C:\snapshot\case_move\node_modules\steam-user\components\familysharing.js
  • C:\snapshot\case_move\node_modules\steam-user\components\friends.js
  • C:\snapshot\case_move\node_modules\steam-user\components\gamecoordinator.js
  • C:\snapshot\case_move\node_modules\steam-user\components\gameservers.js
  • C:\snapshot\case_move\node_modules\steam-user\components\notifications.js
  • C:\snapshot\case_move\node_modules\steam-user\components\pubfiles.js
  • C:\snapshot\case_move\node_modules\steam-user\components\store.js
  • C:\snapshot\case_move\node_modules\steam-user\components\trading.js
  • C:\snapshot\case_move\node_modules\steam-user\components\twofactor.js
  • C:\snapshot\case_move\node_modules\steam-user\index.js
  • C:\snapshot\case_move\index.js
  1. If you want to compile the package/file into executable, please pay attention to compilation warnings and specify a literal in 'require' call. 2) If you don't want to compile the package/file into executable and want to 'require' it from filesystem (likely plugin), specify an absolute path in 'require' call using process.cwd() or process.execPath.
    at Module._resolveFilename (node:internal/modules/cjs/loader:946:15)
    at Function._resolveFilename (pkg/prelude/bootstrap.js:1951:46)
    at Module._load (node:internal/modules/cjs/loader:787:27)
    at Module.require (node:internal/modules/cjs/loader:1012:19)
    at Module.require (pkg/prelude/bootstrap.js:1851:31)
    at require (node:internal/modules/cjs/helpers:102:18)
    at load_lzma (C:\snapshot\case_move\node_modules\lzma\index.js:7:12)
    at Object. (C:\snapshot\case_move\node_modules\lzma\index.js:10:8)
    at Module._compile (pkg/prelude/bootstrap.js:1926:22)
    at Module._extensions..js (node:internal/modules/cjs/loader:1166:10) {
    code: 'MODULE_NOT_FOUND',
    requireStack: [
    'C:\snapshot\case_move\node_modules\lzma\index.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\cdn.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\chat.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\econ.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\familysharing.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\friends.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\gamecoordinator.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\gameservers.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\notifications.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\pubfiles.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\store.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\trading.js',
    'C:\snapshot\case_move\node_modules\steam-user\components\twofactor.js',
    'C:\snapshot\case_move\node_modules\steam-user\index.js',
    'C:\snapshot\case_move\index.js'
    ],
    pkg: true
    }

Node.js v18.5.0
`

Expected Behavior

run without error

To Reproduce

use steam-user lib

github-actions commented

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label

github-actions commented

This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit.