[BUG] A problem with package.json main entry path

🐛 Bug Report

Lib version: 4.0.0 The error is :

Error: Cannot find module 'C:\Users\Nasreddine\Desktop\lab\clean-install\node_modules\exceljs\excel.js'. Please verify that the package.json has a valid "main" entry
    at tryPackage (internal/modules/cjs/loader.js:316:19)
    at Function.Module._findPath (internal/modules/cjs/loader.js:705:18)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:969:27)
    at Function.Module._load (internal/modules/cjs/loader.js:864:27)
    at Module.require (internal/modules/cjs/loader.js:1044:19)
    at require (internal/modules/cjs/helpers.js:77:18)
    at Object.<anonymous> (C:\Users\Nasreddine\Desktop\lab\clean-install\index.js:1:15)
    at Module._compile (internal/modules/cjs/loader.js:1158:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)
    at Module.load (internal/modules/cjs/loader.js:1002:32) {
  code: 'MODULE_NOT_FOUND',
  path: 'C:\\Users\\Nasreddine\\Desktop\\lab\\clean-install\\node_modules\\exceljs\\package.json',
  requestPath: 'exceljs'
}

Steps To Reproduce

I did a clean install of the exceljs and ran it this way

const Excel = require('exceljs');
const workbook = new Excel.Workbook();
const sheet = workbook.addWorksheet('My Sheet');
(async () => {
  await workbook.xlsx.writeFile('out.xlsx');
})();

The expected behaviour:

I expected the package would export a file in the root directory of the project with the name “out.xlsx”

Behaviour in previous version “3.10.0”

Works perfectly with the desired behaviour.

Possible solution (optional, but very helpful):

Change this line in package.json

...
135:    "main": "./excel.js",
...

To

...
135:   "main": "./lib/exceljs.nodejs.js",
...

[alubbe]

@guyonroche the published npm package is missing a few files, most notably excel.js, but also README_zh.md and maybe index.ts. It would be great to include those and publish that as 4.0.1

Also, how did you decide which files and folders to include? If it was manual, should we maybe use an npmignore file instead?

[JLuboff]

Also experiencing this… how did this get released with such a breaking issue?