I have installed Pyramid 1.3.x and pyramid_mongodb scaffold, but it does not appear when I run pcreate --list-templates.
I gather that stuff is registered to work with pyramid scaffolding by making it a [pyramid.scaffold] entry point. In addition, pyramid_mongodb has a dependency on PasteScript (*see update).
The issue is that pyramid_mongodb is missing some information in its setup.py. I've forked the github repo and fixed it so it should work in the future.
Update: The dependency on PasteScript is not entirely the best approach, and I'll update it on github soon. The issue of supporting multiple versions of scaffolding is documented on Pyramid's website
This was not listed for me either but you should still be able to run ./bin/pip install pyramid_mongodb to install with those options.
When you run pserve development.ini, you may get an error pymongo.errors.ConnectionFailure:. If you install MongoDB and run the daemon, your Pyramid app should connect.
Related
I am interested in understanding how to install node-sqlite3, but provide by own precompiled package of sqlite3: I just want to install the Node client and skip the build phase entirely during install.
How can I do this?
(Reasoning: I am going to test the module in multiple environments and have already read countless posts of people having build issues in various environments, so I'd rather manually compile myself.)
It turns out that I was looking for a package like this one:
dblite on npm, GitHub
I have a nodejs package I wish to use - "redis-connect". This is dependent on "hiredis" but seems to be locked at 0.1.7 which does not compile. I am using 7.2.0 nodejs with npm 4.0.3 - problem with node-gyp rebuild. However, hiredis#0.5.0 compiles fine and installs. What's best practise for fixing this dependency so I can install and use redis-connect with hiredis#0.5.0?
There is no "best practice" for something like this. You just have to submit a pull request to the project and convince the maintainer to accept the PR and publish a new version afterwards.
Otherwise you will need to just fork the project and reference that fork (instead of the original project by its name on npm) in your dependencies.
I already have an application created with create-react-app package.
I found a bug with the version of Jest which is 15.1.1. But I realized that in version 16 the bug is gone.
How to update Jest?
My problem is in the package.json of application there is no Jest package.
Jest is in other folder: node_modules/react-scripts.
Create React App updates its dependencies once they are stable enough. This usually means waiting a week or two after the new release.
We don't recommend updating anything by yourself unless this is absolutely critical. If you choose to eject to update something we recommend making it a single commit so that you can revert it later once Create React App uses that version internally.
The following commands are going to get the job done:
npm run eject
npm install --save-dev jest#16.0.0
But be careful here! The eject command irreversibly eliminates the abstraction layer of create-react-app exposing all of the dependencies and configuration to you. Though, your app is going to work just like before. You'll just have total control upon it, including the ability to update dependencies.
I've encountered something in node.js that'd I'd like to submit a patch for. I've also located a Github issue in which somebody also complained about the same annoyance. The issue has been tagged saying that patches are welcome. So, I'd like to try to supply a patch.
But, what's the best way to do this? I've forked the main node repository, and I've located the spots in the C++ code that an adjustment could be made. Before I make these changes though, I am trying to figure out how to test these changes of mine. I've got the official node package installed globally. I'm on Windows. How can I test this modified version of node?
You can install node-gyp to build the addon manually (npm install node-gyp -g). Then just change to the addon's root directory and simply do node-gyp rebuild after you make changes.
After further investigation, the vcbuild.bat produces project files that can simply be opened up with Visual Studio. So, code editing and debugging can all easily be done within VS. Awesome!
It happens occasionally that the development version of a module works in my development workspace and passes on Travis-CI but after publishing to npm it turns-out the end-user package is broken.
For example if you use a sub module that should be in dependencies but had it in devDependencies then CI will pass (but there are plenty other possible breakages).
How do you automate testing this? Do you use external rigging? Is there a secret module? Do you have a user acceptance test suite?
I use Github with Travis-CI but the standard setup uses the development install.
Once upon a time I discovered that npm would let me publish packages that are uninstallable. So I've added a target to my Gruntfile that does this:
Issue npm pack to create a package from my source.
Into a directory created (automatically by my Gruntfile) just for testing install the new package using npm install <path to the package created in the previous step>.
I have a target for publishing a new version that will publish only if the steps above are successful.
The steps above would not catch the dependency problem you mentioned in the question but they could easily be extended to catch it. To do this, I'd add one or more tests that cause the package installed in step 2 above to call require with all that it depends on.
I would suggest to set up your own CI server that does essentially one thing, npm install package ; cd node_modules/package ; npm test. This would ensure that your package is installable at least on your server.
I heard that Jenkins is good for this (at least, that's what node.js core team seems to be using), but don't have any first hand experience yet. We're just planning to set in up in a couple of weeks.
Also, having some external module that depends on you and testing it helps a bit. :)