Django Started yarn install
During installation, warnings appear via the yarn install command. Is this critical for the topic itself? Or can it be ignored?(venv) PS C:\Users\Sportbank\Desktop\Python\Metronix-demo\starterkit\_keenthemes\tools> yarn install
yarn install v1.22.19
warning ..\..\..\..\..\..\package.json: No license field
info No lockfile found.
[1/4] Resolving packages...
warning pdfmake > @foliojs-fork/linebreak > brfs > static-module > magic-string > sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
warning extract-loader > babel-runtime > 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.
warning extract-loader > babel-core > babel-register > core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issu
es. 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.
warning gulp > glob-watcher > chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
warning gulp > glob-watcher > chokidar > fsevents@1.2.13: The v1 package contains DANGEROUS / INSECURE binaries. Upgrade to safe fsevents v2
warning gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
warning gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
warning gulp > glob-watcher > anymatch > micromatch > snapdragon > source-map-resolve > source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
warning gulp-sourcemaps > css > source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
warning rtlcss-webpack-plugin > babel-runtime > 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. Bec
ause 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 compati
bility issues. Please, upgrade your dependencies to the actual version of core-js.
warning webpack-dev-server > webpack-dev-middleware > memfs@3.6.0: this will be v4
[2/4] Fetching packages...
warning chart.js@4.4.0: The engine "pnpm" appears to be invalid.
[3/4] Linking dependencies...
warning " > @yaireo/tagify@4.17.9" has unmet peer dependency "prop-types@^15.7.2".
warning "bootstrap-maxlength > bootstrap@4.6.2" has unmet peer dependency "popper.js@^1.16.1".
warning " > vis-timeline@7.7.2" has unmet peer dependency "@egjs/hammerjs@^2.0.0".
warning " > vis-timeline@7.7.2" has unmet peer dependency "component-emitter@^1.3.0".
warning " > vis-timeline@7.7.2" has unmet peer dependency "keycharm@^0.2.0 || ^0.3.0 || ^0.4.0".
warning " > vis-timeline@7.7.2" has unmet peer dependency "propagating-hammerjs@^1.4.0 || ^2.0.0".
warning " > vis-timeline@7.7.2" has unmet peer dependency "uuid@^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0".
warning " > vis-timeline@7.7.2" has unmet peer dependency "vis-data@^6.3.0 || ^7.0.0".
warning " > vis-timeline@7.7.2" has unmet peer dependency "vis-util@^5.0.1".
warning " > vis-timeline@7.7.2" has unmet peer dependency "xss@^1.0.0".
warning " > postcss-loader@7.3.3" has unmet peer dependency "postcss@^7.0.0 || ^8.0.1".
warning Workspaces can only be enabled in private projects.
[4/4] Building fresh packages...
success Saved lockfile.
Done in 145.41s.
Item Purchase Code:
d611405f-5db6-40d4-9a4f-7407518a35eb
Replies (5)
Hi,
Appreciate your patience. Please note that our support reply time is 24-48 hours. However, we do our best to settle as soon as possible.
Those warnings are not critical and it does not affect the build. Sometimes 3rd-party plugins have minor dependency warnings which we can not control as It depends on those plugin authors.
However, we will try to check and let you know if we can remove some of the warnings.
Just in case Metronic Django does not fulfill your project requirements you may request a refund using Themeforest Refund Form. 100% money back is guaranteed.
Regards, Sean
I changed my rating, I just wanted your reaction.
I am not well versed in JS, I would like to ask you to explain why you need to use Node.JS?
Why compile theme resources?
What is the difference between using just an HTML template?
Hi,
I apologize for the delay. Let me explain the role of Node.js and why theme resources need to be compiled:
Node.js and Compilation:
Node.js is used to compile theme resources, such as styles and scripts, into a format that web browsers can understand.
The raw styles in the theme are often written in SCSS (Sassy CSS), which is a more powerful and flexible way to write CSS. However, web browsers can't directly interpret SCSS; they need CSS.
Node.js takes the SCSS files and compiles them into standard CSS files, which can be understood by web browsers.
Similarly, JavaScript files may be written in a modular or ES6 format, and Node.js helps bundle these scripts into a format that works in browsers.
The Need for Compilation:
Compilation is necessary to optimize and package theme assets efficiently. It also ensures browser compatibility.
Compilation is used to minify and compress assets, reducing load times for users.
It provides the ability to customize styles and functionality by modifying the theme's assets and then recompiling them to see the changes take effect.
You can utilize the pre-existing CSS and JavaScript assets that are provided. However, if you require customization of specific styles or functionality, you'll need to make modifications within the theme's assets and then recompile both the CSS and JavaScript files.
Thanks
https://ru.paste.pics/2d2e08dd1bb368f01dbbe4e8bdc948a5
I tried to install the project on React, but for some reason the select is not displayed correctly. Tell me where to look for the error?
Hi,
In our HTML version, we are using a Select2 plugin for this input element. Since Select2 plugin requires jQuery and combining jQuery with React isn't good practice, Selec2 is not included in our React version by default.
If you want to use Select2 you can include jQuery and install Select2 dependency.
Alternatively, you can consider using react-select dependency.
Please let us know if you have any further questions on this topic or anything else.
Regards,
Lauris Stepanovs,
Keenthemes Support Team
