DylanPiercey on master
Add bundleReadTimeout info to t… (compare)
DylanPiercey on v3.4.0
DylanPiercey on master
3.4.0 docs: update changelog (compare)
DylanPiercey on espree
DylanPiercey on master
feat: switch to espree (#307) (compare)
DylanPiercey on espree
feat: switch to espree (compare)
Hi Guys!
I am using marko and lasso, I intend to be uploading the resources to s3, I would like to be uploading in runtime, but I am having some initial challenges, first which architecture to choose:
There is a possibility to do as suggested in the gist. What do you guys think about this still works?
Or use the lasso-s3-writer plugin, I would not like to be using it since it is necessary to run in prebuild.
Any personal suggestions? Reading? Implementation documentation?
lasso.handleWatchedFileChanged(path);
just invalidates all the caches, so we need to re-run our entire lasso.lassoPage
(which in our case is very slow) everytime a js or marko file changes. Is there any way to invalidate only one specific component (the one that changed) and rebuild only that component instead of running the lasso.lassoPage
for the whole application? (we have a single page app)
/a
/b
/c/routes
/c/components
/c
directory to /c/static
is there a way to exclude routes in /a
and /b
? The behavior that I've seen is that the routes in both a and b end up generating files in the /c/static
directory
/Users/pankaj.bisht/repos/travacation/node_modules/lasso/dist-compat/plugins/lasso-minify-js/index.js:54
throw e;
^
TypeError: Cannot read property 'length' of undefined
at Object.transform (/Users/pankaj.bisht/repos/travacation/node_modules/lasso/dist-compat/plugins/lasso-minify-js/index.js:44:29)
at applyTransform (/Users/pankaj.bisht/repos/travacation/node_modules/lasso/dist-compat/transforms.js:70:30)
at Stream.end (/Users/pankaj.bisht/repos/travacation/node_modules/lasso/dist-compat/transforms.js:34:31)
at _end (/Users/pankaj.bisht/repos/travacation/node_modules/through/index.js:65:9)
at Stream.stream.end (/Users/pankaj.bisht/repos/travacation/node_modules/through/index.js:74:5)
at PassThrough.onend (_stream_readable.js:511:10)
at PassThrough.g (events.js:291:16)
at emitNone (events.js:91:20)
at PassThrough.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
Error: Render async fragment error (lasso-slot:head). Exception: Error: Failed to walk dependency...
errors, usually they are a huge block of text. This is happening when trying to import Amplify.js library. What information should I look for in this error messages?
Hi! I've a problem with lasso-marko-taglib.
with this code:
<lasso-resource path=`./static/${product.url}` var="imgs"/>
<a class="uk-inline" href=`${imgs}` data-caption="Caption 1">
<lasso-img src=`./static/${product.url}` alt=""/>
</a>
Loop product list working good with lasso-img tag ; but with lasso-resource tag is get a error Render error. Exception: ReferenceError: product is not defined
.