Activity

1. maxlath commented on Nov 4, 2014

   

   maxlath

   on Nov 4, 2014

   More actions

   opts.fullPaths only toggles the alternative between having:

   // fullPaths=true
   // [...]
   },{}],"/path/to/modules/":[function(require,module,exports){
   // [...]

   or

   // fullPaths=false
   // [...]
   },{}],33:[function(require,module,exports){
   // [...]
   // and then at the end of the file, the index to
   // to find the full path back
   {"./lib/_stream_duplex.js":33,"./lib/_stream_passthrough.js":58,"./lib/_stream_readable.js":59,"./lib/_stream_transform.js":60,"./lib/_stream_writable.js":61,"/mysystem/myproject/node_modules/browserify/node_modules/readable-stream/readable.js":18,"stream":21}]
   // [...]

   I think your problem is rather similar to this issue #675
2. py-in-the-sky commented on May 29, 2015

   

   py-in-the-sky

   on May 29, 2015

   More actions

   You can now use https://www.npmjs.com/package/bundle-collapser
3. jmm commented on May 29, 2015

   

   jmm

   on May 29, 2015

   Collaborator

   More actions

   @callumlocke What exactly are you trying to accomplish: keep absolute paths out of the bundle? Keep any path data (even relative) out? Please create a repo with a simple reproduction and explanation of how the actual output differs from your desired output.
4. jmm

   added

   repro-please

   on May 29, 2015
5. callumlocke commented on Jul 2, 2015

   

   callumlocke

   on Jul 2, 2015

   Author

   More actions

   @jmm I don't want any paths in the bundle.

   The issue is the statement I quoted from the readme seems to be wrong: it suggests that paths are usually converted into numerical indexes (unless you explicitly enable opts.fullPaths). But in my experience this isn't true, you always get string paths.
6. jmm commented on Jul 2, 2015

   

   jmm

   on Jul 2, 2015

   Collaborator

   More actions

   @callumlocke Ok, thanks for elaborating, I see what you mean. It must have worked that way at one point, but like you said it's obviously inaccurate now. My understanding is that, pretty much what @maxlath said, fullPaths currently toggles absolute local paths instead of relative paths (to the require()'ing file or base dir).

   In any case, as @py-in-the-sky said I think the solution to your problem is bundle-collapser. Can you please take a look and post back here whether that does the trick for you?

   I'm putting a documentation label on this issue to get that description straightened out.

   Thanks!
7. jmm

   added

   documentation

   on Jul 2, 2015
8. goto-bus-stop

   added a commit that references this issue on May 18, 2018

   Clarify fullPaths option, fixes #902.

   This issue will close once commit 03f0004 is merged into the 'master' branch.

   03f0004