Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Cannot read property 'trace' of undefined when using browserify-shim #19

Open
Swatinem opened this issue Aug 5, 2015 · 2 comments

Comments

@Swatinem
Copy link

Swatinem commented Aug 5, 2015

So I’m using browserify-shim to pull in an external dependency from a cdn / browser global.
But when I do that, sorcery via gobble prints the following error:

TypeError: Cannot read property 'trace' of undefined
    at Node.trace (node_modules/gobble/node_modules/sorcery/dist/sorcery.js:715:20)
    at applySegment (node_modules/gobble/node_modules/sorcery/dist/sorcery.js:217:48)
    at Chain.apply (node_modules/gobble/node_modules/sorcery/dist/sorcery.js:264:5)
    at processWriteOptions (node_modules/gobble/node_modules/sorcery/dist/sorcery.js:29:18)
    at Chain.write (node_modules/gobble/node_modules/sorcery/dist/sorcery.js:304:30)

My browserify config (package.json) looks like this:

  "browserify": {
    "transform": [
      "browserify-shim"
    ]
  },
  "browserify-shim": {
    "gl-matrix": "global:window"
  }
@chirayuk
Copy link

I've been experiencing this intermittently for about 1 every 5-6 runs over about 8 or so months now.

TypeError: Cannot read property 'trace' of undefined
    at Node.trace (/Users/chirayu/u/metro/client/node_modules/sorcery/dist/sorcery.cjs.js:472:20)
    at applySegment (/Users/chirayu/u/metro/client/node_modules/sorcery/dist/sorcery.cjs.js:578:48)
    at Chain.apply (/Users/chirayu/u/metro/client/node_modules/sorcery/dist/sorcery.cjs.js:625:5)
    at processWriteOptions (/Users/chirayu/u/metro/client/node_modules/sorcery/dist/sorcery.cjs.js:707:18)
    at Chain.write (/Users/chirayu/u/metro/client/node_modules/sorcery/dist/sorcery.cjs.js:665:30)
    at /Users/chirayu/u/metro/client/node_modules/sorcery/bin/index.js:58:17
    at lib$es6$promise$$internal$$tryCatch (/Users/chirayu/u/metro/client/node_modules/sorcery/node_modules/sander/node_modules/es6-promise/dist/es6-promise.js:331:16)
    at lib$es6$promise$$internal$$invokeCallback (/Users/chirayu/u/metro/client/node_modules/sorcery/node_modules/sander/node_modules/es6-promise/dist/es6-promise.js:343:17)
    at lib$es6$promise$$internal$$publish (/Users/chirayu/u/metro/client/node_modules/sorcery/node_modules/sander/node_modules/es6-promise/dist/es6-promise.js:314:11)
    at lib$es6$promise$asap$$flush (/Users/chirayu/u/metro/client/node_modules/sorcery/node_modules/sander/node_modules/es6-promise/dist/es6-promise.js:125:9)

@mmilad
Copy link

mmilad commented Apr 19, 2017

any news on this issue?
edit again:

looks like its an issue with using the debugger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants