depfu[bot] on update
depfu[bot] on update
Update svgo to version 2.2.1 (compare)
depfu[bot] on check
depfu[bot] on check
Pin postcss to version 8.2.7 (compare)
depfu[bot] on update
papandreou on master
Update open to version 8.0.2 Merge pull request #1155 from a… (compare)
depfu[bot] on update
Update open to version 8.0.2 (compare)
1) transforms/bundleRelations
with the oneBundlePerIncludingAsset strategy
should insert a JS bundle at the point of the last incoming relation:
UnexpectedError:
expected [ Html(testdata/transforms/bundleRelations/insertPoint/HtmlScript.html) ] to satisfy
[
{
type: 'Html',
text: '\n<h1>Hello World</h1>\n<script>var foo = \'foo\';\nvar bar = \'bar\';</script>\n'
}
]
[
Html({
type: 'Html',
url: 'file:///Users/munter/git/assetgraph/testdata/transforms/bundleRelations/insertPoint/HtmlScript.html',
isLoaded: true,
isInline: false,
isRedirect: false
text: '\n<h1>Hello World</h1>\n<script>var foo=\'foo\';var bar=\'bar\'</script>\n'
// should equal '\n<h1>Hello World</h1>\n<script>var foo = \'foo\';\nvar bar = \'bar\';</script>\n'
//
//
// <h1>Hello World</h1>
// <script>var foo='foo';var bar='bar'</script>
// <script>var foo = 'foo';
// var bar = 'bar';</script>
})
]
at Context.<anonymous> (test/transforms/bundleRelations.js:143:7)
set UNEXPECTED_FULL_TRACE=true to see the full stack trace
{
url: undefined,
text: "var foo = 'foo'",
isPretty: false,
matches: null
}
{
url: undefined,
text: "var bar = 'bar'",
isPretty: false,
matches: null
}
isPretty
was undefined
at that point before, isPretty
of the bundle would have been false
I guess
Ah, except, this is the current code in bundleRelations
:
_toBeMinified: assetsToBundle.every(asset => asset._toBeMinified),
isPretty: assetsToBundle.every(asset => asset.isPretty)
and the current code to check if the pretty formatting should be applied is this.isPretty || !this._toBeMinified
bundleAsset.minify()
rollup.config.js
. Thoughts?
Hi guys. <3 I have a quick question - I couldn't find an answer myself from reading the source but I think you'll prob know straight away.
I have a static site I'd like to build with assetgraph-builder. It has quite a few broken relations - from links like <a href="/foo/bar">
meant to target ${root}/foo/bar.html
. The files are going to be served by an nginx with the following config try_files $uri $uri.html $uri/index.html;
.
Is there anyway to teach assetgraph to attempt to resolve a dangling relation by adding .html
to an extension-less URL, without patching the code?
/foo/bar
to /foo/bar/
is not going to fly unfortunately.
.html
when refreshing an incoming relation like the hack for index.html
here: https://github.com/assetgraph/assetgraph/blob/73afa2f66326e66d7f24141bf577df0a1b8e6162/lib/relations/Relation.js#L163-L169