I reported a very similar issue with version 8.1.8, but no matter what I do for version 8.2.0, I can't get it to build in Windows. I have a fresh download of the release package from Themeforest, extracted the blazor\metronic_blazor_v8.2.0_demo1.zip
file and went to the Starterkit\_keenthemes\tools
folder in an administrator command prompt and ran the following commands:
First, yarn install:
C:\temp\metronic\blazor\blazor_demo1\Starterkit\_keenthemes\tools>yarn install
➤ YN0000: ┌ Resolution step
➤ YN0061: │ chokidar@npm:2.1.8 is deprecated: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
➤ YN0061: │ source-map-resolve@npm:0.6.0 is deprecated: See https://github.com/lydell/source-map-resolve#deprecated
➤ YN0061: │ core-js@npm:2.6.12 is 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.
➤ YN0032: │ fsevents@npm:2.3.3: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ fsevents@npm:1.2.13 is deprecated: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2
➤ YN0061: │ source-map-resolve@npm:0.5.3 is deprecated: See https://github.com/lydell/source-map-resolve#deprecated
➤ YN0032: │ nan@npm:2.18.0: Implicit dependencies on node-gyp are discouraged
➤ YN0061: │ resolve-url@npm:0.2.1 is deprecated: https://github.com/lydell/resolve-url#deprecated
➤ YN0061: │ source-map-url@npm:0.4.1 is deprecated: See https://github.com/lydell/source-map-url#deprecated
➤ YN0061: │ urix@npm:0.1.0 is deprecated: Please see https://github.com/lydell/urix#deprecated
➤ YN0061: │ sourcemap-codec@npm:1.4.8 is deprecated: Please use @jridgewell/sourcemap-codec instead
➤ YN0061: │ @npmcli/move-file@npm:2.0.1 is deprecated: This functionality has been moved to @npmcli/fs
➤ YN0002: │ bootstrap-maxlength@npm:1.10.1 doesn"t provide popper.js (p0823b), requested by bootstrap
➤ YN0002: │ keenthemes@workspace:. doesn"t provide @egjs/hammerjs (pdf28f), requested by vis-timeline
➤ YN0002: │ keenthemes@workspace:. doesn"t provide component-emitter (p21463), requested by vis-timeline
➤ YN0002: │ keenthemes@workspace:. doesn"t provide keycharm (p34cfb), requested by vis-timeline
➤ YN0002: │ keenthemes@workspace:. doesn"t provide postcss (pcd48b), requested by postcss-loader
➤ YN0002: │ keenthemes@workspace:. doesn"t provide prop-types (pd44d7), requested by @yaireo/tagify
➤ YN0002: │ keenthemes@workspace:. doesn"t provide propagating-hammerjs (p57e5c), requested by vis-timeline
➤ YN0002: │ keenthemes@workspace:. doesn"t provide uuid (p2998c), requested by vis-timeline
➤ YN0002: │ keenthemes@workspace:. doesn"t provide vis-data (p4d4e7), requested by vis-timeline
➤ YN0002: │ keenthemes@workspace:. doesn"t provide vis-util (p90232), requested by vis-timeline
➤ YN0002: │ keenthemes@workspace:. doesn"t provide xss (p46b14), requested by vis-timeline
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
➤ YN0000: └ Completed in 7s 155ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ yargs-parser@npm:5.0.1 can"t be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:17.7.2 can"t be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yargs@npm:7.1.2 can"t be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yarn-install@npm:1.0.0 can"t be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yocto-queue@npm:0.1.0 can"t be found in the cache and will be fetched from the remote registry
➤ YN0000: └ Completed in 3s 31ms
➤ YN0000: ┌ Link step
➤ YN0000: │ ESM support for PnP uses the experimental loader API and is therefore experimental
➤ YN0007: │ @fortawesome/fontawesome-free@npm:6.4.2 must be built because it never has been before or the last one failed
➤ YN0007: │ core-js@npm:2.6.12 must be built because it never has been before or the last one failed
➤ YN0007: │ es5-ext@npm:0.10.62 must be built because it never has been before or the last one failed
➤ YN0000: └ Completed in 4s 366ms
➤ YN0000: Done with warnings in 14s 851ms
C:\temp\metronic\blazor\blazor_demo1\Starterkit\_keenthemes\tools>gulp
[13:18:52] Local modules not found in C:\temp\metronic\blazor\blazor_demo1\Starterkit\_keenthemes\tools
[13:18:52] Try running: yarn install
npm install
even though the documentation says to run either of them (not both of them):C:\temp\metronic\blazor\blazor_demo1\Starterkit\_keenthemes\tools>npm install
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm WARN deprecated core-js@2.6.12: 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 1544 packages, and audited 1795 packages in 1m
138 packages are looking for funding
run `npm fund` for details
18 vulnerabilities (1 low, 7 moderate, 10 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues possible (including breaking changes), run:
npm audit fix --force
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
C:\temp\metronic\blazor\blazor_demo1\Starterkit\_keenthemes\tools>gulp
file:///C:/temp/metronic/blazor/blazor_demo1/Starterkit/_keenthemes/tools/gulp/helpers.js:16
import {glob} from "glob";
^^^^
SyntaxError: Named export "glob" not found. The requested module "glob" is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:
import pkg from "glob";
const {glob} = pkg;
at ModuleJob._instantiate (node:internal/modules/esm/module_job:122:21)
at async ModuleJob.run (node:internal/modules/esm/module_job:188:5)
at async DefaultModuleLoader.import (node:internal/modules/esm/loader:228:24)
at async importModuleDynamicallyWrapper (node:internal/vm/module:428:15)
Hi Keith,
Can you try to download the latest Metronic v8.2.1?
https://devs.keenthemes.com/metronic/blazor
Regards,
Lauris Stepanovs,
Keenthemes Support Team
Works perfectly, thank you!
Hi,
Glad to hear that. All the best with your project!
Please don't hesitate to reach out if you need anything more from us.
Regards,
Lauris Stepanovs,
Keenthemes Support Team