srveit/mechanize-js

Mechanize is a Javascript library that enables automated web interaction.

mechanize-js's Issues

Session cookies not appearing to work ...

@srveit I'm not sure if session cookies are being maintained throughout get, submit and postForm actions.

The website I am posting to says that there is an error message and that there's no session carried through when I postForm.

Can you comment or can we collaborate on gitter?

Documentation?

Without having to fish through the source, could you provide some documentation? This repo is exactly what I am looking for!

Thanks

An in-range update of jsdoc is breaking the build 🚨

The devDependency jsdoc was updated from 3.6.0 to 3.6.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

jsdoc is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 3 commits.

• 0645930 3.6.1
• bac40ab Parse type applications correctly in Node.js 12. (#1643)
• e5919e4 Update .gitignore.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of ajv is breaking the build 🚨

The dependency ajv was updated from 6.5.4 to 6.5.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

ajv is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 7 commits.

• 494026e 6.5.5
• 6478687 Merge pull request #860 from ossdev07/master
• 2acd5f3 Merge pull request #865 from jsdevel/adding-logger-to-ts
• d5edde4 Merge pull request #871 from nwoltman/patch-1
• 8d769b6 Remove duplicated character in email regex
• ae68416 Adding logger to typescript Options declaration.
• 85b7f52 replacing phantomjs with headless chrome

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

npm package

I noticed that the package in npm is a year old:

https://www.npmjs.org/package/mechanize

It looks like a lot of people are installing it each month. Is it difficult to update the package?

cookiejar import issue?

Hello,

First of all, thank you for your work.
I've tried unsuccessfully to run the submit_form.js with the following error:

ReferenceError: Cookie is not defined
    at Object.<anonymous> (C:\Users\ARC\node_modules\mechanize\bin\submit_form.js:11:14)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.runMain (module.js:604:10)
    at run (bootstrap_node.js:393:7)
    at startup (bootstrap_node.js:150:9)
    at bootstrap_node.js:508:3

Unfortunately, I don't know much about the nodejs import system.
My OS is Windows7, node version is v6.10.2 and npm is v3.10.10

Thanks in advance for your help

An in-range update of eslint-plugin-jasmine is breaking the build 🚨

Version 2.10.0 of eslint-plugin-jasmine was just published.

Branch	Build failing 🚨
Dependency	eslint-plugin-jasmine
Current Version	2.9.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jasmine is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

v2.10.0

<a name"2.10.0">

2.10.0 (2018-05-10)

Features

• rule: add rule to disallow promise without done.fail (9bd0f76e)

Commits

The new version differs by 2 commits.

• 0c29526 fix(docs,tests): add arrow functions in tests, update docs, remove insideReturnStatement
• 9bd0f76 feat(rule): add rule to disallow promise without done.fail

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Can't obtain forms

An in-range update of eslint is breaking the build 🚨

The dependency eslint was updated from 5.15.3 to 5.16.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
• ✅ continuous-integration/appveyor/branch: AppVeyor build succeeded (Details).

---

Release Notes for v5.16.0

• dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567) (Kevin Partington)
• c06d38c Fix: Allow HTML formatter to handle no meta data (#11566) (Ilya Volodin)
• 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548) (Oliver Joseph Ash)
• bc3e427 Update: pass rule meta to formatters RFC 10 (#11551) (Chris Meyer)
• b452f27 Chore: Update README to pull in reviewer data (#11506) (Nicholas C. Zakas)
• afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550) (Vernon de Goede)
• 4fe7eb7 Chore: use nyc instead of istanbul (#11532) (Toru Nagashima)
• f16af43 Chore: fix formatters/table test (#11534) (Toru Nagashima)
• 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528) (Teddy Katz)

Commits

The new version differs by 11 commits.

• ded2f94 5.16.0
• ea36e13 Build: changelog update for 5.16.0
• dfef227 Build: gensite passes rulesMeta to formatter rendering (#11567)
• c06d38c Fix: Allow HTML formatter to handle no meta data (#11566)
• 87a5c03 Docs: func-style: clarify when allowArrowFunctions is used (#11548)
• bc3e427 Update: pass rule meta to formatters RFC 10 (#11551)
• b452f27 Chore: Update README to pull in reviewer data (#11506)
• afe3d25 Upgrade: Bump js-yaml dependency to fix Denial of Service vulnerability (#11550)
• 4fe7eb7 Chore: use nyc instead of istanbul (#11532)
• f16af43 Chore: fix formatters/table test (#11534)
• 78358a8 Docs: fix duplicate punctuation in CLI docs (#11528)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Cannot Start Node

When i start node your project: node bin/get_page.js
and get errrors bellow:
/home/thiensubs-linux/Documents/mechanize-js/node_modules/libxmljs/node_modules/bindings/bindings.js:79
throw e
^
Error: /home/thiensubs-linux/Documents/mechanize-js/node_modules/libxmljs/build/Release/xmljs.node: undefined symbol: _ZN2v82V837AdjustAmountOfExternalAllocatedMemoryEl
at Error (native)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at bindings (/home/thiensubs-linux/Documents/mechanize-js/node_modules/libxmljs/node_modules/bindings/bindings.js:74:15)
at Object. (/home/thiensubs-linux/Documents/mechanize-js/node_modules/libxmljs/lib/bindings.js:1:99)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)

"this.doc" is null when performing page.search

Hi Stephen, thanks for the module. I'm trying to do a simple form submit, but it doesn't seem to be working.

 br = mechanize.newAgent()
    br.get({uri:'https://login.yahoo.com/config/login_verify2?&.src=ym&.intl=us'}, function(err, page){
        var f = page.form('login_form');
        f.setFieldValue('login','myUsername');
        f.setFieldValue('passwd','myPassword');
        f.submit(function(err, page){
            console.log(page);
        }); 
    }); 

When I run this, I get: cannot "find" of null on page.search(xpath)

Can you help? Thanks.

Comparison with PhantomJS

How does mechanize-js compare to PhantomJS?

Support?

Apart from the lacking documentation.
I've noticed that this library has been unmaintained for 10 months and no replies from the owner.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴