This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
prompt
dependency breaking tns builds and a possible solution
#211
Milestone
Hi,
I just added nativescript-plugin-firebase to an app and my build started breaking with the following error
This seems to be caused by nativescript-cli trying to copy the
prompt
"dependency" to the device output folder, and failing when it tries to update executable symlinks. We have a number of issues here culminating in that problem:prompt
needing to be a dependency, while it should really be a dev dependency. It is needed only by the postinstall script, but if it is a dev dependency, npm would not download it to a project.tns
copying more files than it needs to. I'll open a separate issue about skipping executable symlinks.nativescript-telerik-ui had a similar problem and they chose to get rid of the
prompt
dependency by bundling it in their postinstall script. I can open a PR that does the same fornativescript-plugin-firebase
.In addition I'll open issues on nativescript-cli that will prevent copying symlinks and allow plugin authors to prevent their postinstall scripts from being copied to mobile devices by providing a way to exclude certain files from device builds.
My question for @EddyVerbruggen here is whether you'll consider a PR implementing a webpack-based workflow for the postinstall script that will solve the immediate problem.
The text was updated successfully, but these errors were encountered: