I would like to know what is the best way at the moment to use PostgreSQL instead of MongoDb with MeteorJS.
I'm using meteor 1.8 and I found the package https://github.com/numtel/meteor-pg but to make it work i need this package : https://github.com/numtel/meteor-pg-server but when i install it i have this error :
meteor add numtel:pg-server
=> Errors while adding packages:
While checking for numtel:pg-server#1.0.1:
error: No compatible binary build found for this package. Contact the package author and ask them to publish it
for your platform.
I think it's not compatible with meteorJS 1.8 ...
So i found another package : https://github.com/Richie765/meteor-pg
And the problem with this one is when I install it, I have this error :
meteor npm install meteor-pg --save
added 26 packages from 47 contributors and audited 1904 packages in 5.961s
found 2 vulnerabilities (1 low, 1 high)
run npm audit fix to fix them, or npm audit for details
meteor npm audit fix
up to date in 2.264s
fixed 0 of 2 vulnerabilities in 1904 scanned packages
2 vulnerabilities required manual review and could not be updated
meteor npm audit
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Cross-Site Scripting
Package bootstrap-tagsinput
Patched in No patch available
Dependency of bootstrap-tagsinput
Path bootstrap-tagsinput
More info https://nodesecurity.io/advisories/124
Low Prototype Pollution
Package lodash
Patched in >=4.17.5
Dependency of modernizr
Path modernizr > lodash
More info https://nodesecurity.io/advisories/577
I think this problem came because I'm using an Admin template which is : Angle - Bootstrap Admin Template (http://wrapbootstrap.com/preview/WB04HF123) because when i restart my project, there is the following error :
Unable to resolve some modules:
"jquery.flot.spline/jquery.flot.spline.js" in /C/Users/R-D/Desktop/meteor/imports/startup/client/vendor.js
(web.browser.legacy)
"jqueryui-touch-punch/jquery.ui.touch-punch.min.js" in
/C/Users/R-D/Desktop/meteor/imports/startup/client/vendor.js (web.browser.legacy)
If you notice problems related to these missing modules, consider running:
meteor npm install --save jquery.flot.spline jqueryui-touch-punch
so i execute meteor npm install --save jquery.flot.spline jqueryui-touch-punch then :
npm ERR! code E404
npm ERR! 404 Not Found: jquery.flot.spline#latest
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\R-D\AppData\Roaming\npm-cache_logs\2018-11-26T10_35_09_102Z-debug.log
I'm sorry if my problem is dumb, i'm a young developper and it's the first framework i'm using.
Best regards.
you can you use it with any database you want but you will lost the real meteor fell like real time data and other cool feature meteor have
you can use https://node-postgres.com/ for the installation and use Meteor.wrapAsync() for the operation
Related
I have an Artifactory server (service). I set up a local repository there that I am using for hosting Unity packages. I figured out how to setup scoped packages that Unity Package Manager can see. It's all working pretty well. My only issue is with command line deploying of the artifacts. From what I read it looks like I need to use "npm publish" to deploy. When I call npm "publish" on the tarball file (package file) that I have, it doesn't get uploaded (deployed) to the server. I have to manually upload it using the web UI. The command itself doesn't fail - it prints out list of files, version, name, etc. And ends with something like this
<package name>#x.x.x
What is the point of the (npm) publish command if that's not how you upload (deploy) packages? What is the proper way to upload packages to Artifactory without using the web interface?
Btw, I started with this tutorial: Medium Article. I get similar output when i run publish command locally, so it seems like that should be uploading the package for me, but it doesn't. Another note: i do use scoped packages - i used all of the instructions that Artifactory and that tutorial provides. I get no errors anywhere. Just nothing happens when i publish.
Any suggestions?
Edit:
This is the command I run:
npm publish <packagename>.x.x.x.tgz --registry http://<server>artifactory/api/npm/unity_packages/<scope>
I saw this thread thread, but I would rather not use curl (i have to replicate this setup on various machines, so less moving parts is better for me) and it is also super old, so i figured there is a newer / better way to deploy.
Edit2: I can also "npm install" packages that I deployed using the web UI, so I do't think it's a permission issue.
Edit3: Sample output:
npm publish --registry http://artifactory.ops.aws.somecompany.net/artifactory/api/npm/unity_packages/
npm notice
npm notice 📦 #com.somecompany/com.somecompany.dependencypackageproject#0.1.207
npm notice === Tarball Contents ===
npm notice 388B DependencyPackageProject.asmdef
npm notice 611B Source/Floater.cs
npm notice 1.1kB package_internal.json
npm notice 1.1kB package.json
npm notice 2.1kB Material/FloaterMaterial.mat
npm notice 166B DependencyPackageProject.asmdef.meta
npm notice 155B Scenes/DPP_SampleScene.unity.meta
npm notice 243B Source/Floater.cs.meta
npm notice 182B Material/FloaterMaterial.mat.meta
npm notice 154B Prefabs/FloaterPrefab.prefab.meta
npm notice 172B Material.meta
npm notice 158B package_internal.json.meta
npm notice 158B package.json.meta
npm notice 172B Prefabs.meta
npm notice 172B Scenes.meta
npm notice 172B Source.meta
npm notice 4.0kB Prefabs/FloaterPrefab.prefab
npm notice 10.3kB Scenes/DPP_SampleScene.unity
npm notice === Tarball Details ===
npm notice name: #com.somecompany/com.somecompany.dependencypackageproject
npm notice version: 0.1.207
npm notice package size: 5.5 kB
npm notice unpacked size: 21.4 kB
npm notice shasum: 77188f8f599877d7a6a41bbcb1800057a3fe1646
npm notice integrity: sha512-vbtkwkiEacQl/[...]dPb8xlhO36odg==
npm notice total files: 18
npm notice
+ #com.somecompany/com.somecompany.dependencypackageproject#0.1.207
In order to publish a scoped npm package to Artifactory using the npm client you need to:
(1) Make sure your package is created as a scoped package as described in the npm documentation
(2) Associate the relevant Artifactory npm repository (for example npm-local) with the scope you are using, by updating your .npmrc configuration file. The file should also contain the authentication information.You can follow the instructions in the Artifactory documentation. Your .npmrc file should look similar to the following:
#drorb:registry=http://localhost:8081/artifactory/api/npm/npm-local/
//localhost:8081/artifactory/api/npm/npm-local/:_password=*********
//localhost:8081/artifactory/api/npm/npm-local/:username=drorb
//localhost:8081/artifactory/api/npm/npm-local/:email=*****#gmail.com
//localhost:8081/artifactory/api/npm/npm-local/:always-auth=true
(3) Use the npm publish command, for example
npm publish craftyjs-npm-example-1.0.0.tgz --registry http://localhost:8081/artifactory/api/npm/npm-local/
Output of the publish command should be similar to
npm notice
npm notice 📦 #drorb/craftyjs-npm-example#1.0.0
npm notice === Tarball Contents ===
npm notice 662B package.json
npm notice 587B .npmignore
npm notice 116B README.md
npm notice 195B game.js
npm notice === Tarball Details ===
npm notice name: #drorb/craftyjs-npm-example
npm notice version: 1.0.0
npm notice package size: 1.6 kB
npm notice unpacked size: 1.6 kB
npm notice shasum: 8ee8bdbfac6ae92fcdcdc7441793671ce59a3584
npm notice integrity: sha512-4DA3LCwO+vuCo[...]FYPGTtxOrg6UQ==
npm notice total files: 4
npm notice
I followed Microsoft docs for setting the SharePoint framework. https://learn.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment But when I got to the point where you are supposed to install the generator it gives me this error.
>>
PS C:\Users\jakub.yaghob> npm install #microsoft/generator-sharepoint -g
>>
npm WARN notsup Unsupported engine for got#5.7.1: wanted: {"node":">=0.10.0 <7"}
(current: {"node":"12.13.0","npm":"6.13.0"})
>>
npm WARN notsup Not compatible with your version of node/npm: got#5.7.1
>>
+ #microsoft/generator-sharepoint#1.9.1
updated 1 package in 8.851s
I have tried older versions of node.js but either they were too old for them to work with the new npm or they were too new to work with the generator.
Any help would be greatly appreciated. Thanks!
The current supported LTS version of NodeJS for the SharePoint Framework is both Node.js v8.x and Node.js v10.x. You need install Node.js for v8.x or v10.x.
Download Node.js: https://nodejs.org/en/download/releases/
I was also facing this issue. I found if Installed version 8.x.x of Node and then ran
npm install -g npm#5
This would lower the version of npm and allow me to install the generator.
I'm only getting started with Node and npm so have no idea what the impact of doing this is. However, it did work as I was able to run npm list -g --depth=0 and see the generator had been installed.
#ibm -
I'm getting following error while trying to publish loopback application on IBM Cloud using API Designer portal. Please help me understand why is it looking into Temp folder to publish the application and how I can bypass that. I keep getting resource busy or locked issue with apiconnect toolkit.
Here's the node, npm and apiconnect toolkit version I'm using currently. Please let me know if you need any additional details.
node - v8.9.4
npm - v5.6.0
apiconnect - v5.0.8.2 (apiconnect: v2.7.111)
Error publishing runtime: Command failed: npm prune --production npm
ERR! path
C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json.1443453620
npm ERR! code EBUSY npm ERR! errno -4082 npm ERR! syscall rename npm
ERR! EBUSY: resource busy or locked, rename
'C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json.1443453620'
-> 'C:\Users\SUNNY~1.GOE\AppData\Local\Temp\0.6717806509437265-1517290270545\project\node_modules\cryptiles\node_modules\boom\package.json'
npm ERR! A complete log of this run can be found in: npm ERR!
C:\Sunny\npm-cache_logs\2018-01-30T05_31_21_546Z-debug.log Error ID:
a055ee2d-8232-459b-bf62-f4340837a61b
As a simple step, first run this command from cli
apic stop all
and try the publishing loopbaclk application to IBM Bluemix.
In case, this does not resolve the issue, then the problem may be due to permission issues during the installation of APIC toolkit. Uninstall the toolkit do a fresh install of toolkit using '--unsafe-perm' option with the install command to overrides the permisson issues Here is the example
sudo npm install --unsafe-perm -g apiconnect
Try the publish with the new instance of API Connect and see if it resolves the issue.
After cloning the project code from the Repository, I'm trying to install the npm to update the packages and plugins included. The command used is:
npm install
It worked well for previous clones. But now it displays the following error:
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents#1.0.12
npm WARN appname# No repository field.
npm WARN appname# No license field.
When I tried to install fsevents using --verbose, it is said that the supported OS is Darwin. But it worked in the previous clone. Why not now?
If your a Windows user:
The fsevents warning isn't a problem. It's an optional dependency and isn't needed for this to work on Windows.
But the error still displaying, in order to fix this.
Open package.json and delete the gulp-watch dependecy
Manualy remove the folder (gulp-watch) from the node_modules fordel
Unload the Project and uploaded again
The error is gone!!!
There's a issue open to fix this in .net core , but this will work untill then.
Does anyone have an updated guide for installing node-xmpp from start to finish on either Cent OS or Ubuntu's latest builds?
I have attempted installing but continue to get the following error:
Cannot load StringPrep-0.1.0 bindings. You may need to `npm install node-stringprep'
This is the log for stringprep:
root#node-xmpp:~/node-latest-install# npm install node-stringprep
npm http GET https://registry.npmjs.org/node-stringprep
npm http 200 https://registry.npmjs.org/node-stringprep
npm http GET https://registry.npmjs.org/node-stringprep/-/node-stringprep-0.1.5.tgz
npm http 200 https://registry.npmjs.org/node-stringprep/-/node-stringprep-0.1.5.tgz
> node-stringprep#0.1.5 install /root/node-latest-install/node_modules/node-stringprep
> node-gyp rebuild
make: Entering directory `/root/node-latest-install/node_modules/node-stringprep/build'
CXX(target) Release/obj.target/node-stringprep/node-stringprep.o
SOLINK_MODULE(target) Release/obj.target/node-stringprep.node
SOLINK_MODULE(target) Release/obj.target/node-stringprep.node: Finished
COPY Release/node-stringprep.node
make: Leaving directory `/root/node-latest-install/node_modules/node-stringprep/build'
node-stringprep#0.1.5 node_modules/node-stringprep
I had exactly this problem installing node-xmpp on a Fedora 17 system.
The solution for me was yum install libicu-devel
libicu "provides Unicode and Globalization support for software applications" and I guess the up-to-date version of this is needed by node-xmpp.
See https://github.com/astro/node-stringprep
I've exactly this problem installing node-xmpp on a Debian 6 system.
I use apt-get install libicu-dev, I've upgrade node, follow this issue https://github.com/astro/node-stringprep/issues/32 but the problem is not solve