[v2] - Error: ENOENT: no such file or directory, open '//data.trie'

[tafelito]

Describe the bug
I think updating to the new version of textkit in this commit 3a5bb34 breaks the build using webpack

I've been using the v2.beta in a nextjs app and everything was working fine until beta.14. As soon as I updated to beta.17 I started to get this error. I googled it and it seems that a few people had that issue and webpack with pdfkit, so I assumend it had to do with the update of textkit to v0.4

Desktop (please complete the following information):

• OS: MacOS
• Browser NA
• React-pdf version 2.beta.17

[Mario8419]

same problem here, it was working with beta.14. Any idea or how is it going in general with mobile support @diegomura ?

[tomaswitek]

@tafelito @Mario8419 are you using next.js? If yes, what kind of build target did you use in your next.config.js?
I started to have this kind of problem after changing the build target from server to serverless.
I think it's related to this issue: foliojs/pdfkit#990

[Mario8419]

sry, I'm on gatsby. solved the enoent problem with proper state handling...the problem occurs if you do have to much rerenderings. ;)

[tomaswitek]

@Mario8419 thx for the info

[tomaswitek]

I found a workaround for next.js serverless apps.
This commit should fix the issue.
It's inspired by https://github.com/Pzixel/PDFKit-example

[tomaswitek]

Hey @diegomura,
I think updating unicode-properties should resolve this issue: foliojs/unicode-properties#2
I tried to prepare a PR, but the original repo is quite different to yours :(

[diegomura]

This is fixed in the last versions. Thanks!