All geek questions in one place

The npm publish module includes the iOS infrastructure. When npm installs this module, the iOS infrastructure is corrupted

This is the weirdest issue, and it only happens on one iOS infrastructure (as I noticed) in the npm module.

when I click on the framework (before npm is published) I see:

frameworkname.framework | - Headers (dir) - frameworkname - Versions (dir) | -A (dir) -Current (dir)

I published this module on a private npm server. When I install the npm module, the structure is damaged. I see:

 frameworkname.framework | - Headers (dir) MISSING - frameworkname MISSING - Versions (dir) | -A (dir) -Current (dir) MISSING

After reading http://www.raywenderlich.com/65964/create-a-framework-for-ios, it seems that the missing files are symbolic links. Has anyone else seen this behavior before? How to save symbolic links during npm process?

+6
source share
1 answer

Missing files are symbolic links, and unfortunately npm does not support symbolic links. As a workaround, you can replace links with your goals (and remove goals to prevent duplication).

eg. for the FFF frame with the structure:

 ./FFF -> Versions/Current/FFF ./Headers -> Versions/Current/Headers ./Versions ./Versions/A ./Versions/A/FFF ./Versions/A/Headers ./Versions/Current -> A

you can run the following (in bash) from the framework directory:

 framework=FFF && rm $framework Headers && mv Versions/A/{$framework,Headers} . && rm -rf Versions

to change the structure to:

 ./FFF ./Headers
0
source

Source: https://habr.com/ru/post/984524/

More articles:


All Articles