bit-bin/dist/consumer/component/templates/postinstall.default-template.js

<a href="https://opensource.org/licenses/Apache-2.0"><img alt="apache" src="https://img.shields.io/badge/License-Apache%202.0-blue.svg"></a> <a href="https://github.com/teambit/bit/blob/master/CONTRIBUTING.md"><img alt="prs" src="https://img.shields.io/b

"use strict";

Object.defineProperty(exports, "__esModule", {
  value: true
});
exports.default = void 0;

/**
 * code template for writing link files.
 * when custom module resolution was originally used by the author, we create link-files on
 * node_modules directory upon importing the component. this way, when the code is looking for a
 * relative file with a module path (e.g. `require ('@/is-string')`), it'll find it.
 *
 * Now, here is the problem, when the component is installed by npm/yarn, Bit can't create these
 * link files. That's where this post install script comes it. It creates the missing link files
 */
var _default = (linkFilesStr, symlinkFilesStr) => {
  return `var fs = require('fs');
var path = require('path');

var linkFiles = ${linkFilesStr};
var symlinks = ${symlinkFilesStr};

function ensureDir(filePath) {
  var dirname = path.dirname(filePath);
  if (fs.existsSync(dirname)) {
    return true;
  }
  ensureDir(dirname);
  fs.mkdirSync(dirname);
}

Object.keys(linkFiles).map(function (linkFile) {
  if (!fs.existsSync(linkFile)) {
    ensureDir(linkFile);
    fs.writeFileSync(linkFile, linkFiles[linkFile]);
  }
});
Object.keys(symlinks).map(function (symlink) {
  if (!fs.existsSync(symlink)) {
    ensureDir(symlink);
    var existingFile = require.resolve(symlinks[symlink]);
    fs.symlinkSync(existingFile, symlink);
  }
});
`;
};

exports.default = _default;