forked from faassen/bowerstatic
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGES.txt
44 lines (32 loc) · 1.42 KB
/
CHANGES.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
CHANGES
*******
0.4 (unreleased)
================
- Nothing changed yet.
0.3 (2014-08-28)
================
- BowerStatic failed to initialize if a component was discovered
without a ``main``. These are handled now -- if you try to include a
path to such a resource, no extra inclusions are generated. Fixes #5.
- If ``main`` was an array, only the first such resource was
loaded. The correct behavior should be to load all these
resources. This required a reworking of how resources get created;
instead of creating a single resource for a path, a list of
resources is created everywhere. Fixes #6 (and was mentioned in #5).
- Introduce a ``component(name)`` method on the components
object. Given a component name it will give an object that has a
``url()`` method. This can be used to obtain the URL of a component
directory, which is sometimes useful when client-side code needs to
construct URLs itself, such as for templates. Fixes issue #8.
- You can register a renderer for a particular extension type using,
for example, ``bower.renderer('.js', render_js)``, where
``render_js`` takes a URL and should return a string with a HTML
snippet to include on the page.
0.2 (2014-07-18)
================
- Even if the same resource is included multiple times, it will only
be included once. Thanks Ying Zhong for the bug report and suggested
fix.
0.1 (2014-07-07)
================
- Initial public release.