Skip to content

0.2.8 MODULE_NOT_FOUND when requiring @xivapi/nodestone #19

@EkoBean

Description

@EkoBean

Hi! The latest npm package seems to be published with an invalid "main" entry (MODULE_NOT_FOUND on require).

node -e "require('@xivapi/nodestone')"

Error: Cannot find module 'X:\xxxxxxxxx\node_modules\@xivapi\nodestone\src\index.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (node:internal/modules/cjs/loader:500:19)
    at Function._findPath (node:internal/modules/cjs/loader:760:18)
    at Function._resolveFilename (node:internal/modules/cjs/loader:1351:27)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1021:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1026:22)
    at Function._load (node:internal/modules/cjs/loader:1175:37)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
    at Module.require (node:internal/modules/cjs/loader:1445:12)
    at require (node:internal/modules/helpers:135:16) {
  code: 'MODULE_NOT_FOUND',
  path: '\\\\?\\X:\\xxxxxxxxx\\node_modules\\@xivapi\\nodestone\\package.json',
  requestPath: '@xivapi/nodestone'
}

It looks like the published package.json points to an entry file that doesn't exist in the published output.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions