Possible issue with certain path format about browserify-shim

[thlorenz]

It looks like you are using a config that's compatible with browserify-shimv2.
I would suggest to upgrade to v3 and adapt your shim config to match this format. You will have to use it directly in that case (instead of through grunt-browserify).

Off the bat I'd think that your path should start with a ./.
Have you filed an issue with grunt-browserify?

It is very hard for me to diagnose problems when browserify-shim is not used via the intended API.

[knownasilya]

@thlorenz thanks for the reply. If I use the new format, how can I keep browserify as part of my watch task in grunt without using grunt-browserify?

[thlorenz]

At this point you can't because grunt-browserify works with the older version see this comment.

If you want to keep using grunt-browserify then you'd have to stick with the older version.
However you don't need a grunt watch task. You can either use watchify instead or just rebundle when the bundle is requested while you are developing like I demonstrated here.

I'd recommend that (rebundling on demand) since you want to avoid build steps as much as possible.

Alternatively if you don't run your own server, but are mainly just trying to write a client side app, I highly recommend beefy.
If you are using an express server I recommend appup or any of the tools listed here.

[knownasilya]

Do you have any examples of browserify-shim working with browserify-middleware for express?

[thlorenz]

No, I personally don't, but possibly those repos have examples and/or you could look through their tests.