Support Prisma client generation

[ehmicky]

Prisma generates its client logic during postinstall and outputs it to node_modules/.prisma (using ${__dirname}/../../.prisma).

This does not work with zip-it-and-ship-it due to the reason outlined here.

We should add some logic to support Prisma's use case.

[ehmicky]

A workaround could be the following: when we retrieve the list of published files (files field from package.json of a Node module), we could add the following logic: if module is @prisma/client, then add ${__dirname}/../../.prisma/** to the list of published files, providing that directory exists.

Note that .prisma does not have any dependencies itself, apart from requiring @prisma/client. And all files inside .prisma/** should be published.

@timsuchanek, could you confirm this would work as intended?

[timsuchanek]

Thanks @ehmicky, that's exactly what we need!

[ehmicky]

Done in #103.
Could you please check the PR and make sure this is doing what you would like? Thanks!

[ehmicky]

This has been released in @netlify/zip-it-and-ship-it@0.4.0-16. Could you please confirm this is fixing your problem? When you do, I will release this to production.

[timsuchanek]

Thanks a lot @ehmicky for looking into this. I can confirm that this is indeed working now!