Comments (7)
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.
Related Issues (20)
- Packages/paths with .js in the name cannot be used
- 2.0 does not support build_profile option in bundle configuration HOT 23
- Assetic filter with production flag causes 404 errors in dev environment HOT 13
- assetic:dump --watch keeps generating files HOT 1
- Setting hide_unoptimized_assets to false causes an InvalidConfigurationException HOT 5
- extra template neccessary for require.js HOT 1
- require_js Twig global no longer created
- Almond integration
- How can I use modules for r.js? HOT 2
- Service ("templating.helper.assets") on cache:clear
- directories specified in the array "paths" in yml configuration file are not processed correctly
- Twig Exception about Template name...
- Undefined method HOT 7
- Incorrect <script> output in production
- Create a recent tag HOT 1
- Fix src() method in RequireJSHelper.php HOT 1
- Use this bundle with php templating engine (not twig)
- enable JS File loading from public folders to increase performance in development HOT 1
- Multiple bundles? HOT 1
- The child node "base_directory" at path "hearsay_require_js" must be configured. HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hearsayrequirejsbundle.