int3/jsshaper — comment on commit c18505c090d582671f715621290f2f0d19a65fe2
File:  line 0
By olov:

Right, the tools I was thinking about was more along the lines of browserify, which AFAIU assemble together CommonJS-style modules so that they can be used in the browser. But it introduces an inconvenient compilation step of course. [When I wrote "It already works in the browser" I was thinking about the triplet-technique currently used in Shaper]

I think AMD is a reasonable compromise, and I'm OK with landing such a pull request. One thing I'm curious about is whether it supports paths relative to the top-level directory instead of relative to the current file? I found that convenient in the current code-base, especially not having to think about whether to import "fmt.js" or "../fmt.js" depending on whether I'm creating a plugin or not. But perhaps always-relative paths is the way to go for other reasons.

I like your approach to AMD with Narcissus.