The knowledge from superlumen

knowledge's People

Contributors

Stargazers

Watchers

knowledge's Issues

Absolute vs relative paths

When importing from meteor...

I read somewhere that relative is preferred, but this issue makes it seem like absolute is the preference. Unclear. I prefer absolute.

Bug in meteor up / react 0.14.4

The fix is here.

Edit /usr/lib/node_modules/mup/lib/build.js (might instead be at /usr/local/lib/node_modules/mup/lib/build.js).

function archiveIt(buildLocaltion, callback) {
  callback = _.once(callback);
  var bundlePath = pathResolve(buildLocaltion, 'bundle.tar.gz');
  var sourceDir = pathResolve(buildLocaltion, 'bundle');

+  var esprimaFolder = sourceDir+'/programs/server/npm/react-runtime-prod/node_modules/react/node_modules/envify/node_modules/jstransform/node_modules/esprima-fb/';
+  if(fs.existsSync(esprimaFolder+'#README.md#')){
+   fs.renameSync(esprimaFolder+'#README.md#',esprimaFolder+'.#README.md');
+  }

Or here's the standalone snippet to copy & paste:

  var esprimaFolder = sourceDir+'/programs/server/npm/react-runtime-prod/node_modules/react/node_modules/envify/node_modules/jstransform/node_modules/esprima-fb/';
  if(fs.existsSync(esprimaFolder+'#README.md#')){
    fs.renameSync(esprimaFolder+'#README.md#',esprimaFolder+'.#README.md');
  }