Closed oliviertassinari closed 4 years ago
I use the following fix for now in the package on userspace.
package.json
"postinstall": "cd node_modules/wordpos && yarn postinstall"`
However, we lose ~1s for each yarn interaction, not great
Hmm.. ran into this too. After running your script seeing ENOENT: no such file or directory, scandir '/dict'
.
Any movement on this? Still having this issue and yarn only seems to be growing in popularity. The postinstall
fix is a fine temp one, but is definitely a performance hit.
I can't reproduce with latest yarn:
~/dev/tmp/wordpos-yarn-test$ yarn
yarn install v1.9.4
(node:81202) ExperimentalWarning: The fs.promises API is experimental
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
[4/4] 📃 Building fresh packages...
success Saved lockfile.
✨ Done in 5.50s.
~/dev/tmp/wordpos-yarn-test$ ls node_modules/wordnet-db/dict/
data.adj data.verb fast-index.noun.json index.adv index.verb
data.adv fast-index.adj.json fast-index.verb.json index.noun
data.noun fast-index.adv.json index.adj index.sense
Please try updating yarn
.
@moos Did you run yarn twice?
Yes -- I did. I was able to repro with earlier version of yarn, but not with latest.
~~Can confirm that this is fixed in yarn>1.9.4. Thanks for checking this @moos
Take it back. Just added a package and got a no such file or directory /node_modules/wordnet-db/dict/fast-index.noun.json'
. Adding back the post install line got me back up and running
I have noticed the following behaviour trying to install wordpos with yarn.
During the first install
wordnet-db
fast indexDuring a consecutive,
yarn
thing get messywordnet-db
folder changed and reset it to his original state. However, aswordpos
is still the same, his postinstall script isn't call.