Skip to content

issues Search Results · repo:browserify/module-deps language:JavaScript

Filter by

61 results
 (129 ms)

61 results

inbrowserify/module-deps (press backspace or delete to remove)

browserify/module-deps
Unexpected token with ?.

I m not sure if the problem is here (or in a subpackage, like detective, but I noticed this library tripping over semi-recent ES syntax. I m not sure what the best fix is - if there s something on my end ...
  • xavdid
  • Opened 
    on Jun 29, 2021
  • #166

browserify/module-deps
Module-deps@4.1.1 asyncWrite is not a function

In file _stream_writable.js process-nextick-args module imported. var processNextTick = require( process-nextick-args ); processNextTick - is an object not a function. So this line of code var asyncWrite ...
  • Apindes
  • 2
  • Opened 
    on Aug 26, 2020
  • #165

browserify/module-deps
File content randomly truncated in large projects

When using browserify on a large project we regularily see errors such as: Parse Error: Line 233: Unexpected end of input while parsing file: ... The errors don t occur in a consistent file or line, the ...
  • mgilfillan
  • 4
  • Opened 
    on Feb 11, 2020
  • #162

browserify/module-deps
Are module-deps options passed as parameter to the transforms?

The documentation is unclear about this point: If the transform is a function, it should take the file name as an argument Then, the example shows a second parameters named opts: var through = require( ...
  • ericmorand
  • 1
  • Opened 
    on Nov 27, 2019
  • #160

browserify/module-deps
How to retrieve the file where an error occurred?

I m trying to retrieve the file where an error occurred and all I m able to catch is a standard JavaScript error with a message but not file. For example: index.js const mdeps = require( module-deps ...
  • ericmorand
  • 3
  • Opened 
    on Nov 25, 2019
  • #159

browserify/module-deps
Project dead?

Is this project dead? Is it looking for maintainers? What is the status?
  • codebling
  • Opened 
    on Nov 2, 2019
  • #158

browserify/module-deps
Use native Object.assign instead of xtend

xtend can easily be replaced with Object.assign This reduce the dependencies and possible also avoid duplicated versions where some package don t use the same version range for the xtend package // immutable ...
  • jimmywarting
  • Opened 
    on Oct 15, 2018
  • #153

browserify/module-deps
Incompatibility with global-style

So this just caused me major headache: if you have global-style active in your npmrc, browserify won t find dependencies of your dependencies. It would be very helpful if browserify were able to locate ...
  • mvastola
  • 6
  • Opened 
    on Sep 15, 2018
  • #151

browserify/module-deps
options.paths not used for transforms

Hi, Is there any reason why you dont pass paths in loadTransforms? I had some transforms installed in a separate directory referenced by NODE_PATH. node find them correctly but browserify not even if I ...
  • fk-hb
  • 4
  • Opened 
    on Jul 29, 2018
  • #150

browserify/module-deps
module-deps seems incompatible with node-resolve

See https://stackoverflow.com/q/51347558/1198896 for the detailed background, but basically, given the following minimal testcase: test.js: require( ./test2.js ); test2.js: (empty) test3.js: var resolve ...
  • strugee
  • Opened 
    on Jul 16, 2018
  • #149
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub