RequireJS 2.0 support and other improvements about hearsayrequirejsbundle HOT 7 CLOSED

Currently looking into the baseUrl and paths bugs :)

As for the RequireJS src, for now you can load a local version by specifying an alternate initialize_template which extends 'HearsayRequireJSBundle::initialize.html.twig' and overrides the src block. That's something of a hack, though - currently my thought is to allow specifying either a URL or a template name as the src config option. If a template name is given, it'll be rendered to generate the src URL - that way you can use Assetic or whatever to process a local file, and spit out an asset URL to use for the RequireJS src.

Shim is also high priority - currently I'm thinking it should just live in the bundle config, similar to paths. Though in general, as the set of available RequireJS options gets more complex, I'm starting to wonder if there's a good way for the bundle to support more generic configuration setups, particularly for optimization. Writing the optimizer as an Assetic filter introduces some tricky inconsistencies with the "standard" methods of optimizing a RequireJS project, mainly because it forces optimization to happen file-at-a-time rather than directory-at-a-time. Any thoughts on a better configuration API are certainly welcome :)

from hearsayrequirejsbundle.

Correct, I overwrote the initialize.html.twig template, but the integration with Assetic with a custom route could be a better option.

I think shims fit on the bundle config too, although it would be optimal to dynamically generate a js config file and then dump it for Assetic processing. This way we can take advantage of some bundle processing, but still being able to tweak the settings without having to create more bundle configuration options. In a certain way, you can already do this with the initialize template, but probably not as cleanly :)

I wonder if we can run the r.js optimizer without Assetic - possibly using a Twig tag ({% requirejs %}) - that way we could take advantage of all the features of this build tool (or others, such as grunt). Not sure if this is reinventing the wheel though...

from hearsayrequirejsbundle.

Any updates on this one?

from hearsayrequirejsbundle.

in config.yml write in requirejs section:

require_js_src: /path/to/require.min.js

from hearsayrequirejsbundle.

I have some thoughts after reading this issue. I think possible to implement the ability to customize configuration options for each bundle using some namespaces which are reflect the bundle names. In addition, specify some global configuration options which will be applied to each bundle with the ability to override the latter at the bundle level configuration. What do you think?

from hearsayrequirejsbundle.

@ruimarinho, at this moment we don't have only the ability to specify a local path to the RequireJS via the require_js_src. Can you confirm? I'll add the last and close this issue. Thanks!

from hearsayrequirejsbundle.

I've added the ability to specify the local path to the RequireJS. If you have any questions, create a new issue please. Thanks!

from hearsayrequirejsbundle.