ironmansoftware / powershell-universal

Issue tracker for PowerShell Universal
https://powershelluniversal.com
36 stars 4 forks source link

Custom Javascript component build fails #3638

Open MikeShepard opened 2 months ago

MikeShepard commented 2 months ago

Steps to Reproduce

Follow instructions in https://blog.ironmansoftware.com/universal-dashboard-custom-components/

Invoke-Build fails with "Copy-Item : Cannot find path 'C:\Users\WDAGUtilityAccount\testPSUComponent\public' because it does not exist."

(Even if you create the public folder before invoke-build)

Expected behavior

Invoke-Build succeeds

Actual behavior

PS C:\Users\WDAGUtilityAccount\testPSUComponent> invoke-build
Build . C:\Users\WDAGUtilityAccount\testPSUComponent\component.build.ps1
Task /./Build

added 861 packages, and audited 862 packages in 21s

27 packages are looking for funding
  run `npm fund` for details

90 vulnerabilities (2 low, 50 moderate, 33 high, 5 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

> component@1.0.0 build
> webpack -p --env production

    Directory: C:\Users\WDAGUtilityAccount\testPSUComponent

Mode                 LastWriteTime         Length Name                                                                                                                   
----                 -------------         ------ ----                                                                                                                   
d-----         8/22/2024   6:26 PM                output                                                                                                                 
ERROR: Cannot find path 'C:\Users\WDAGUtilityAccount\testPSUComponent\public' because it does not exist.
At C:\Users\WDAGUtilityAccount\testPSUComponent\component.build.ps1:16 char:2
+     Copy-Item $PSScriptRoot\public\*.* $OutputPath
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At C:\Users\WDAGUtilityAccount\testPSUComponent\component.build.ps1:3 char:1
+ task Build {
+ ~~~~~~~~~~~~
Build FAILED. 2 tasks, 1 errors, 0 warnings 00:00:23.3117572
Copy-Item : Cannot find path 'C:\Users\WDAGUtilityAccount\testPSUComponent\public' because it does not exist.
At C:\Users\WDAGUtilityAccount\testPSUComponent\component.build.ps1:16 char:2
+     Copy-Item $PSScriptRoot\public\*.* $OutputPath
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\Users\WDAGUt...omponent\public:String) [Copy-Item], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

Additional Environment data

This was running in a bare windows 11 sandbox environment with fresh installs of everything (but it matches what I got on an in-use box).

Screenshots/Animations

No response

adamdriscoll commented 2 months ago

I think it's eating the JS build error. Try running npm run build in the source directory. Can you also let me know what version of node you are using?

npm -v
node -v
MikeShepard commented 2 months ago

PS C:\dev\testPSUComponent> npm run build

@.*** build webpack -p --env production

'webpack' is not recognized as an internal or external command, operable program or batch file.

PS C:\dev\testPSUComponent> npm -v 10.8.2 PS C:\dev\testPSUComponent> node -v v20.17.0

On Sun, Aug 25, 2024 at 10:27 AM Adam Driscoll @.***> wrote:

I think it's eating the JS build error. Try running npm run build in the source directory. Can you also let me know what version of node you are using?

npm -v node -v

— Reply to this email directly, view it on GitHub https://github.com/ironmansoftware/powershell-universal/issues/3638#issuecomment-2308895885, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKI2ISKLTMRME7FR62SSBTZTHZXFAVCNFSM6AAAAABM7DH3O2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYHA4TKOBYGU . You are receiving this because you authored the thread.Message ID: @.***>

-- https://powershellstation.com

MikeShepard commented 2 months ago

PS C:\dev\testPSUComponent> npm install -g webpack

added 76 packages in 6s

9 packages are looking for funding run npm fund for details PS C:\dev\testPSUComponent> npm run build

@.*** build webpack -p --env production

CLI for webpack must be installed. webpack-cli (https://github.com/webpack/webpack-cli)

We will use "npm" to install the CLI via "npm install -D webpack-cli". Do you want to install 'webpack-cli' (yes/no): y Installing 'webpack-cli' (running 'npm install -D webpack-cli')... npm warn old lockfile npm warn old lockfile The package-lock.json file was created with an old version of npm, npm warn old lockfile so supplemental metadata must be fetched from the registry. npm warn old lockfile npm warn old lockfile This is a one-time fix-up, please be patient... npm warn old lockfile npm warn deprecated @.: Please see https://github.com/lydell/urix#deprecated npm warn deprecated @.: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated @.: See https://github.com/lydell/source-map-resolve#deprecated npm warn deprecated @.: See https://github.com/lydell/source-map-url#deprecated npm warn deprecated @.: Rimraf versions prior to v4 are no longer supported npm warn deprecated @.: https://github.com/lydell/resolve-url#deprecated npm warn deprecated @.: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated @.: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm warn deprecated @.: This SVGO version is no longer supported. Upgrade to v2.x.x. npm warn deprecated @.: This package is no longer supported. npm warn deprecated @.: Please upgrade to v0.1.5 npm warn deprecated @.: Please update to ini >=1.3.6 to avoid a prototype pollution issue npm warn deprecated @.: Please upgrade to v0.1.7 npm warn deprecated @.: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated @.: Glob versions prior to v9 are no longer supported npm warn deprecated @.: This package is no longer supported. npm warn deprecated @.: flatten is deprecated in favor of utility frameworks such as lodash. npm warn deprecated @.: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. ( https://github.com/visionmedia/debug/issues/797) npm warn deprecated @.: This package is no longer supported. npm warn deprecated @.: This is probably built in to whatever tool you're using. If you still need it... idk npm warn deprecated @@.: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs ( https://babeljs.io/docs/en/babel-polyfill) for more information. npm warn deprecated @@.: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead. npm warn deprecated @@.: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead. npm warn deprecated @@.: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm warn deprecated @@.: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead. npm warn deprecated @@.: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead. npm warn deprecated @@.: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead. npm warn deprecated @.: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm warn deprecated @.: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm warn deprecated @.: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. ( https://github.com/visionmedia/debug/issues/797) npm warn deprecated @.: support for ECMAScript is superseded by uglify-js as of v3.13.0 npm warn deprecated @.: Please upgrade to v1.0.1 npm warn deprecated @.: Please upgrade to v1.0.1 npm warn deprecated @.: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. ( https://github.com/visionmedia/debug/issues/797) npm warn deprecated @.: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm warn deprecated @.: Please upgrade to v1.0.1 npm warn deprecated @.: Please upgrade to v1.0.1 npm warn deprecated @.: Please upgrade to v1.0.1 npm warn deprecated @.: Please upgrade to v1.0.1 npm warn deprecated @.: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm warn deprecated @.: Please upgrade to v1.0.1 npm warn deprecated @.: Please upgrade to v1.0.1 npm warn deprecated @.: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools. npm warn deprecated @.: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. ( https://github.com/visionmedia/debug/issues/797) npm warn deprecated @.***: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 861 packages, and audited 862 packages in 17s

27 packages are looking for funding run npm fund for details

90 vulnerabilities (2 low, 50 moderate, 33 high, 5 critical)

To address issues that do not require attention, run: npm audit fix

To address all issues (including breaking changes), run: npm audit fix --force

Run npm audit for details. Error: Cannot find module 'webpack-cli/package.json' Require stack:

C:\Users\mike.SHEPARD\AppData\Roaming\npm\node_modules\webpack\bin\webpack.js at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15) at Function.resolve (node:internal/modules/helpers:190:19) at runCli (C:\Users\mike.SHEPARD\AppData\Roaming\npm\node_modules\webpack\bin\webpack.js:78:26) at C:\Users\mike.SHEPARD\AppData\Roaming\npm\node_modules\webpack\bin\webpack.js:178:5 at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { code: 'MODULE_NOT_FOUND', requireStack: [

'C:\Users\mike.SHEPARD\AppData\Roaming\npm\node_modules\webpack\bin\webpack.js' ] }

On Sun, Aug 25, 2024 at 10:43 AM Mike Shepard @.***> wrote:

PS C:\dev\testPSUComponent> npm run build

@.*** build webpack -p --env production

'webpack' is not recognized as an internal or external command, operable program or batch file.

PS C:\dev\testPSUComponent> npm -v 10.8.2 PS C:\dev\testPSUComponent> node -v v20.17.0

On Sun, Aug 25, 2024 at 10:27 AM Adam Driscoll @.***> wrote:

I think it's eating the JS build error. Try running npm run build in the source directory. Can you also let me know what version of node you are using?

npm -v node -v

— Reply to this email directly, view it on GitHub https://github.com/ironmansoftware/powershell-universal/issues/3638#issuecomment-2308895885, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKI2ISKLTMRME7FR62SSBTZTHZXFAVCNFSM6AAAAABM7DH3O2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYHA4TKOBYGU . You are receiving this because you authored the thread.Message ID: @.***>

-- https://powershellstation.com

-- https://powershellstation.com