I have recently written a yeoman generator called 'generator-webvr-decorator'. Following the instructions from this post, I have done all the steps including publishing to npm. However, after four days I do still not see my generator listed under the yeoman generators web page. The number of generators seems to be frozen at 3438.
I have done all the following:
npm test passes.
I have 'yeoman-generator' in the package.json keywords:
```
{
"name": "generator-webvr-decorator",
"version": "0.1.5",
"description": "add WebVr boilerplate to an existing application",
"license": "MIT",
"main": "app/index.js",
"repository": "vt5491/generator-webvr-decorator",
"author": {
"name": "vt5491",
"email": "vt5491#gmail.com",
"url": "https://github.com/vt5491"
},
"scripts": {
"test": "mocha"
},
"files": [
"generators",
"lib"
],
"keywords": [
"yeoman-generator",
"webvr",
"vr",
"angular"
],
"dependencies": {
"async": "^1.5.0",
"chalk": "^1.0.0",
"cheerio": "^0.19.0",
"escope": "^3.3.0",
"esprima": "^2.7.0",
"jquery": "^2.1.4",
"jsonfile": "^2.2.3",
"lodash": "^3.10.1",
"merge": "^1.2.0",
"yeoman-generator": "^0.19.0",
"yosay": "^1.0.2"
},
"devDependencies": {
"mocha": "*"
}
}
```
published to npm. It is found by the npm search:
turner#vturner-virtual-machine ~/vtstuff/github2/generator-webvr-decorator $ npm search
generator-webvr-decorator
NAME DESCRIPTION AUTHOR DATE VERSION KEYWORDS
generator-webvr-decorator add WebVr boilerplate to an existing application =vt5491 2015-12-05 0.1.4 yeoman-generator webvr vr
Manually tested installing from the npm repository under windows and linux, so I know it physically works assuming yeoman does some kind of automated testing i.e checks to see if the generator actually runs.
Can anyone see what I'm doing wrong?
How often is the database of generators under yeoman.io updated?
Should I open a ticket with the yeoman web site?
I don't know what the add rate for generators is, but in the last four days the generator count has stayed constant at 3438.
Many Thanks.
The system fetching new generators is currently down: https://github.com/yeoman/yeoman-generator-list/issues/38 - It'll hopefully be up in the next few days.
We're also currently posting packages with yeoman-generator keywords that we exclude for other reason here: https://github.com/yeoman/yeoman-generator-list/issues/36 (I don't see yours in there, so your generator will show up soon)
Related
After building the electron application using electron-builder, I cannot open the application from the dist folder. I did change all my links to use path.join(__dirname, "relative_path/") as what I have seen in some answers here. But I can't open the application even though the packaging process is successful.
File structure for the electron app project
Here's an image of my file structure, and this is the package.json file of the project
{
"name": "my_little_reminder",
"version": "0.5.0",
"description": "A simple time reminder app",
"main": "src/index.js",
"scripts": {
"start": "electron .",
"test": "jest --coverage",
"build": "electron-builder --dir"
},
"author": "Leonlit",
"license": "MIT",
"dependencies": {
"node-notifier": ">=8.0.1",
"node-schedule": "^1.3.2",
"sqlite3": "^5.0.0",
"electron-log": "^4.3.1"
},
"devDependencies": {
"electron": "^11.2.1",
"electron-builder": "^22.9.1",
"jest": "^26.6.3"
}
}
Finally, here's a link to the repository if the information here is not enough, https://github.com/Leonlit/My-Little-Reminder/tree/development
Resolved the issue by adding and using the npm script "postinstall": "electron-builder install-app-deps".
Then, using path.join(app.getPath('userData'), '/tasks.db') instead of path.join(__dirname, '/tasks.db') for the sqlite database storage location.
Finally, changed a link in the index file which caused the application to always request for saving a ASAR file on app launch if left unfixed.
My dialogflow project has encountered the following error message that I have been unable to resolve. Has anyone encountered such an issue and aware of how to resolve this?
dialogflowFirebaseFulfillment
Warning, estimating Firebase
Config based on GCLOUD_PROJECT.
Initializing firebase-admin may
fail
I am thinking that there may be an issue with my package.json file:
{
"name": "dialogflowFirebaseFulfillment",
"description": "This is the default fulfillment for a Dialogflow agents using Cloud Functions for Firebase",
"version": "0.0.1",
"private": true,
"license": "Apache Version 2.0",
"author": "Google Inc.",
"engines": {
"node": "8"
},
"scripts": {
"start": "firebase serve --only functions:dialogflowFirebaseFulfillment",
"deploy": "firebase deploy --only functions:dialogflowFirebaseFulfillment"
},
"dependencies": {
"actions-on-google": "^2.2.0",
"firebase-admin": "^8.9.0",
"firebase-functions": "^3.2.0",
"dialogflow": "^0.6.0",
"dialogflow-fulfillment": "^0.6.1"
}
}
The warning message is only that - a warning. It does not mean there is a problem.
If you are not using firebase-admin calls, then you have nothing to worry about.
If you are using firebase-admin, then you just need to be sure that the environment is referencing the project you expect.
Update
The "slow execution" is likely due to the Cloud Function cold starting - the environment had been shut down or otherwise wasn't running, so it needs to initialize and setup the environment. On subsequent calls, within a reasonable time, it should already be running and you won't experience the slowdown.
I've been having this issue for a while and I've even opened an issue on electron-builder github page but haven't received any response.
I'm running electron builder version 20.38.4 and trying to package the app for Win 64 environment. Everything works fine when I do "yarn dev" and "yarn compile". Even "yarn dist" works without any issue.
However, when I click on the generated .exe file, I get this error message.
Any ideas?
Here's the link to the issue I've opened with some detailed screenshots and log outputs
https://github.com/electron-userland/electron-builder/issues/3561
Here's the package.json as requested
{
"name": "myproj",
"version": "0.0.0",
"license": "MIT",
"scripts": {
"dev": "electron-webpack dev",
"compile": "electron-webpack",
"dist": "yarn compile && electron-builder",
"dist:dir": "yarn dist --dir -c.compression=store -c.mac.identity=null"
},
"dependencies": {
"#rodrigogs/mysql-events": "^0.5.2",
"electron-online": "^1.0.0",
"mysql": "^2.16.0",
"source-map-support": "^0.5.9"
},
"devDependencies": {
"electron": "3.0.10",
"electron-builder": "^20.38.4",
"electron-webpack": "^2.6.1",
"webpack": "^4.26.0"
},
"build": {
"appId": "com.teamio.app",
"productName": "Teamio",
"buildVersion": "1.0",
"copyright": "Copyright © 2018 Teamio.app",
"nsis": {
"oneClick": false,
"perMachine": true,
"allowElevation": true,
"allowToChangeInstallationDirectory": true,
"deleteAppDataOnUninstall": true,
"createDesktopShortcut": true,
"installerIcon": "build/icon.ico",
"uninstallerIcon": "build/icon.ico",
"uninstallDisplayName": "Uninstall Teamio"
},
"win": {
"target": "nsis",
"icon": "build/icon.ico"
}
}
}
Sorry to revive an old question, but what is happening is the electron-online package does not properly define its dependencies in its own package.json. So it is missing the debug package, which you have "solved" by placing another package that requires debug in your project dependencies. In reality though, the (long abandoned) package electron-online should update its dependencies and add debug, among others.
As a slightly cleaner workaround, you could add debug to your project dependencies instead of electron-webpack or webpack.
I had the same problem a few hours ago, resolved by not excluding (ignoring) the src folder from package config. Could you paste you package.json file here ?
Ok. Looks like I've solved my own problem. Not sure why exactly but it worked. What I had to do was move 2 dependencies listed below from devDependencies to dependencies section in my package.json
"electron-webpack": "^2.6.1",
"webpack": "^4.26.0"
If someone can shed some light on that, it'd be helpful. I figured I'd post it here in case someone else runs into this issue.
I create desktop application by using electron, and tried electron-packager.
But electron-packager doesn't package node modules which names are started from "#" (Example: #turf, #mapbox)
In node_modules folder of developing folder, I can find "#turf" and "#mapbox".
But after running
>electron-packager . MaplatEditor --platform=darwin --arch=x64 --electron-version=1.7.9
Created package never includes "#turf" and "#mapbox".
And also, it's depending modules are also not included.
My package.json includes "#turf", so it is not setting error.
{
"name": "MaplatEditor",
"version": "1.0.0",
"description": "",
"main": "lib/main.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"#turf/turf": "^4.6.1",
"argv": "0.0.2",
"async": "^2.5.0",
"child_process": "^1.0.2",
"electron-json-storage": "^3.2.0",
"file-url": "^2.0.2",
"fs-extra": "^3.0.1",
"imagemagick": "^0.1.3",
"mapshaper": "^0.4.31",
"path": "^0.12.7",
"wellknown": "^0.5.0"
}
}
How can I package such #-started modules into application package?
In my case, I updated #Turf module for latest version, then electron-packager worked well.
I don't know why, but it looks not the issue of electron-packager...
Since the current VS code doesn't support Electron v1.6, so I have to downgrade my Electron version. However, I found that I can not install the old version of Electron by giving the version number in the package.json file. The following is my configuration:
{
"name": "Example",
"version": "1.0.0",
"description": "",
"main": "./app/main.js",
"scripts": {
"postinstall": "install-app-deps",
"start": "electron ."
},
"keywords": [],
"author": "",
"license": "ISC",
"devDependencies": {
"electron-builder": "^15.5.1",
"electron": "^1.4",
"electron-rebuild": "^1.5.7"
},
"dependencies": {
"jquery": "^3.1.1",
"sqlite3": "^3.1.8"
}
}
The output of the npm install is the following:
And I run the following command to check the version of Electron:
node_modules/.bin/electron -v
and the output is '1.6.2' which is the latest version of Electron.
What's more interesting is that I can install the old version of Electron successfully by directly running the following command:
npm install electron#1.4
So I want to if there is anything wrong in my package.json file which caused this problem. And if so, how can I fix it.
Actually, the Electron version 1.6 satisfies "^1.4" because the caret tells NPM the minimal version of the package to install.
As also written in an answer to the Microsoft issue on GitHub, you might use "1.4" or "~1.4.0" in order to get Electron 1.4 or any other 1.4.x version (the tilde is for minimal minor releases as shown in the NPM documentation for the cli-based update of packages).