question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

electronize doesn't add `version` or `description` to the package.json it uses in a build.

See original GitHub issue

Using the latest version (11.5.1)

This is causing a build error for linux targets with a message of Please specify 'version' in the package.json and also causes a warning with message of description is missed in the package.json

Steps to Reproduce:

  1. add a version and description to the package.json in the application
  2. execute electronize /target linux on a linux system (other steps may need to be done here to get linux building correctly)
  3. look at the package.json used during electronize call and notice its not there.

the file used during the electronize call is put in this general location ~/obj/desktop/-encodedCommand/package.json

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
BenjaminVettoricommented, Feb 25, 2021

It seems that name, author and version are only written to package.json and package-lock.json, if the “buildVersion” value is set: https://github.com/ElectronNET/Electron.NET/blob/master/ElectronNET.Host/build-helper.js

electron.manifest.json:

{
  "name": "Example-App",
  "author": "The Author",
  ...
  "build": {
    "appId": "com.my.app",
    ...
    "buildVersion": "1.0.0",
    ...
  },
  ...
}
0reactions
GregorBiswangercommented, Mar 28, 2023

🎉🚀 New Electron.NET version 23.6.1 released 🚀🎉

With native Electron 23 and .NET 6 support. Your problem should be fixed here. If you continue to have the problem, please let us know. Please note the correct updating of your API & CLI. Info in the README. Have fun!

Read more comments on GitHub >

github_iconTop Results From Across the Web

electronize build does not produce output in \bin\desktop ...
I try to build my electron app using the command "electronize build /target win" but no output is produced in the \bin\desktop folder....
Read more >
package.json
Description. This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just...
Read more >
Adding dependencies to a package.json file
To see which versions of a package will be installed, use the semver calculator. "dependencies" : Packages required by your application in production....
Read more >
Building Cross-Platform Desktop Apps with Electron.NET
This article provides a walkthrough for developing and deploying an application with Electron.NET. Topics covered include:.
Read more >
Common Configuration
To package Proton Native app, set protonNodeVersion option to current or specific NodeJS version that you are packaging for. Currently, only macOS and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found