Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Cannot read properties of undefined (reading 'assets') #11

Open
Tom-H2oThermo opened this issue Oct 23, 2024 · 2 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@Tom-H2oThermo
Copy link

Describe the bug
When I run "npm start" I'm getting a number of errors.

To Reproduce
Steps to reproduce the behavior:
run "npm build" and "npm start". At first I was getting about 89 errors with long cryptic error explanations. this page https://stackoverflow.com/questions/64557638/how-to-polyfill-node-core-modules-in-webpack-5 says that this issue happens when your webpack module gets upgraded from V4 to V5, which must have happened when I ran "npm build". That same page said that a solution was to install the node-polyfill-webpack-plugin which I did. Then the number of errors were reduced to 10 relatively simple errors, but I don't know how to fix them.

Expected behavior
I expected the "npm start" to work and open my Excel app/taskpane.

Screenshots or logs/output in Terminal Please see the errors below.
**PS C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1> npm start

[email protected] prestart
npm run build
[email protected] build
webpack --mode production
C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\webpack\lib\Compilation.js:4706
if (buildInfo.assets) {
^
TypeError: Cannot read properties of undefined (reading 'assets')
at Compilation.createModuleAssets (C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\webpack\lib\Compilation.js:4706:18)
at C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\webpack\lib\Compilation.js:3196:13
at Compilation._runCodeGenerationJobs (C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\webpack\lib\Compilation.js:3351:11)
at C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\webpack\lib\Compilation.js:3181:12
at C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\webpack\lib\Compilation.js:3443:6
at C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\neo-async\async.js:2818:7
at done (C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\neo-async\async.js:3522:9)
at C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\webpack\lib\Compilation.js:3404:8
at C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\webpack\lib\Compilation.js:3521:5
at C:\Users\tomte\OneDrive\Documents\GitHub\H2oThermo_App-Development1\node_modules\enhanced-resolve\lib\forEachBail.js:39:13

Node.js v18.20.2**

Environment(please complete the following information):

  • OS: Microsoft Windows 11 Home
  • Version 10.0.22361
  • VS Code Version 1.94.2
  • Node Version 18.20.2
@hermanwenhe
Copy link
Contributor

Is this project created from a hello world template or from a sample in sample gallery?

@hermanwenhe
Copy link
Contributor

The npm build script won't upgrade the webpack. Have you done the upgrade yourself? After a new project is setup, the only thing you need to do before npm start is npm install.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants