# Sentiment@2.1.1 dependency?

**URL:** <https://discourse.nodered.org/t/sentiment-2-1-1-dependency/18840>\
**Category:** General\
**Created:** [5 December 2019 22:32 UTC](https://discourse.nodered.org/t/sentiment-2-1-1-dependency/18840 "2019-12-05T22:32:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RobP](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@RobP](https://discourse.nodered.org/u/RobP)\
**Post date:** [5 December 2019 22:32 UTC](https://discourse.nodered.org/t/sentiment-2-1-1-dependency/18840/1 "2019-12-05T22:32:32Z")

</div>

I have been successfully building my docker image of node-red based on alpine for a couple weeks now, and I have an "update coreutils" in there before the build. Within the last couple days, the build no longer works and results in an error:

```auto
npm ERR! code ETARGET
npm ERR! notarget No matching version found for sentiment@2.1.1
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget 
npm ERR! notarget It was specified as a dependency of 'node-red-node-sentiment'
npm ERR! notarget

```

The full debug.log from a manual install of sentiment@2.1.1:

```auto
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'install',
1 verbose cli 'sentiment@2.1.1' ]
2 info using npm@6.4.1
3 info using node@v8.16.2
4 verbose config Skipping project config: /usr/src/node-red/.npmrc. (matches userconfig)
5 verbose npm-session d29c4d37a77aeb38
6 silly install loadCurrentTree
7 silly install readLocalPackageData
8 http fetch GET 304 https://registry.npmjs.org/sentiment 85ms (from cache)
9 silly registry:manifest no matching version for sentiment@2.1.1 in the cache. Forcing revalidation
10 http fetch GET 304 https://registry.npmjs.org/sentiment 22ms (from cache)
11 silly fetchPackageMetaData error for sentiment@2.1.1 No matching version found for sentiment@2.1.1
12 timing stage:rollbackFailedOptional Completed in 0ms
13 timing stage:runTopLevelLifecycles Completed in 680ms
14 verbose type version
15 verbose stack sentiment: No matching version found for sentiment@2.1.1
15 verbose stack at pickManifest (/usr/local/lib/node_modules/npm/node_modules/npm-pick-manifest/index.js:65:11)
15 verbose stack at fetchPackument.then.packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:52:18)
15 verbose stack at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
15 verbose stack at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
15 verbose stack at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
15 verbose stack at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
15 verbose stack at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
15 verbose stack at Async._drainQueue (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
15 verbose stack at Async._drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
15 verbose stack at Immediate.Async.drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
15 verbose stack at runCallback (timers.js:810:20)
15 verbose stack at tryOnImmediate (timers.js:768:5)
15 verbose stack at processImmediate [as _immediateCallback] (timers.js:745:5)
16 verbose cwd /usr/src/node-red
17 verbose Linux 3.10.0-957.el7.x86_64
18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "sentiment@2.1.1"
19 verbose node v8.16.2
20 verbose npm v6.4.1
21 error code ETARGET
22 error notarget No matching version found for sentiment@2.1.1
23 error notarget In most cases you or one of your dependencies are requesting
23 error notarget a package version that doesn't exist.
24 verbose exit [1, true]

```

Has anyone seen this problem? I'm not sure how to investigate or fix, and now I can't build my images so my development has come to a standstill.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [5 December 2019 22:59 UTC](https://discourse.nodered.org/t/sentiment-2-1-1-dependency/18840/2 "2019-12-05T22:59:59Z")

</div>

> [@RobP](#):
>
> node-red-node-sentiment

Hi @RobP

I've just published v0.1.6 of node-red-node-sentiment node to fix this. Not sure how the 2.1.1 dependency got in there as no such version exists. I've reverted it to 2.1.0 which does.

---

<div class="post-metadata">

**Author:** ![RobP](https://avatars.discourse-cdn.com/v4/letter/r/b2d939/32.png) [@RobP](https://discourse.nodered.org/u/RobP)\
**Post date:** [5 December 2019 23:08 UTC](https://discourse.nodered.org/t/sentiment-2-1-1-dependency/18840/3 "2019-12-05T23:08:27Z")

</div>

Wow, that's what I call customer service. Thanks so much! (I was wondering why all of a sudden it works when I didn't make any changes).