How to check logs of which packages updated?


#1

Hi! I made a post a little over a week ago about Selenium-Webdriver. I managed to get it working and everything was working until now. I noticed upon opening my glitch project that there was a lot of the following message:

Resolving: total x, reused y, downloaded z

which lasted for a couple minutes. Then, suddenly, my webdrivers weren’t working anymore. My assumption is that one of my packages updates and may have messed things up? I was wondering if there was a way to check what’s been updated/changed to see if I can rollback. Thanks!

I’ve included the error message below just in case but I don’t think it’s too relevant:

    at earlyTermination.catch.e (/rbd/pnpm-volume/5c14e12f-0790-4195-ba5f-0315077802ad/node_modules/.registry.npmjs.org/selenium-webdriver/3.6.0/node_modules/selenium-webdriver/remote/index.js:252:52)

    at <anonymous>

    at process._tickCallback (internal/process/next_tick.js:189:7)

From: Task: WebDriver.createSession()

    at Function.createSession (/rbd/pnpm-volume/5c14e12f-0790-4195-ba5f-0315077802ad/node_modules/.registry.npmjs.org/selenium-webdriver/3.6.0/node_modules/selenium-webdriver/lib/webdriver.js:769:24)

    at Function.createSession (/rbd/pnpm-volume/5c14e12f-0790-4195-ba5f-0315077802ad/node_modules/.registry.npmjs.org/selenium-webdriver/3.6.0/node_modules/selenium-webdriver/phantomjs.js:220:41)

    at createDriver (/rbd/pnpm-volume/5c14e12f-0790-4195-ba5f-0315077802ad/node_modules/.registry.npmjs.org/selenium-webdriver/3.6.0/node_modules/selenium-webdriver/index.js:170:33)

    at Builder.build (/rbd/pnpm-volume/5c14e12f-0790-4195-ba5f-0315077802ad/node_modules/.registry.npmjs.org/selenium-webdriver/3.6.0/node_modules/selenium-webdriver/index.js:657:16)

Thanks!


#2

Seems like my problem fixed itself over time… Unsure of what happened, but I’ll take it :slight_smile:


#3

I’m having a potentially-related problem where it seem that a package that I’ve installed from github is being cached. I’ve updated a file on github, but that update is not being reflected in the package even though it is being re-installed by glitch.

Edit: Ended up just renaming my repo :\


#4

Did that package have a different version number? Running enable-pnpm should force a re-build of the cache which might help to force updates through.


#5

I’m not sure what you mean about package number, sorry - I was just importing it directly from github like this:

"dependencies": {
    ...
    "mypackage": "git+https://github.com/username/repo-name.git",
    ...
}

Will enable-pnpm work for direct github imports?


#6

That’s right.

You can add a commit to ‘version’ them e.g. git+https://github.com/username/package.git#commit, then updating that commit flags the updated content. More about this here: https://docs.npmjs.com/files/package.json#git-urls-as-dependencies.