Open Sandeepv68 opened 6 years ago
austinkelleher
commented
6 years ago Hey, @SandeepVattapparambil. I'm going to need a bit more information in order to help you. What version of Lasso are you using? Are you using marko-starter? Is this happening when you run a build? If it's coming from a component, perhaps you could isolate the issue and post a code sample. Thanks.
Sandeepv68
commented
6 years ago I am using marko "^4.7.0" and lasso "^2.11.21". This happens when the build happens and when i hit a route. and this is from a component
Sandeepv68
commented
6 years ago This problem persists on lasso version above ^2.11.21 and not on 2.11.21 and below "lasso": "2.11.21" is not making any problem
austinkelleher
commented
6 years ago @SandeepVattapparambil Can you try upgrading to the latest marko and latest lasso-marko?
maxmilton
commented
6 years ago I'm also running into this issue. Using marko-starter. Still an issue with all packages at the latest version.
Occurs when using any lasso plugins, e.g. project.js:
module.exports = require('marko-starter').projectConfig({
lassoConfig: {
plugins: [
'lasso-marko',
'lasso-stylus',
],
},
});The relevant part of my package.json
"dependencies": {
"marko": "^4.7.4",
},
"devDependencies": {
"lasso-marko": "^2.4.0",
"lasso-postcss": "^0.1.1",
"marko-starter": "^2.0.2",
},After debugging a some more, this bug only happens when a .marko file has
style {
...
}Possibly also related to this, if a .marko file as a class {} then all the styles loaded and then quickly removed — a flash of styled content. In this case there are no errors or warnings reported.
maxmilton
commented
6 years ago After more playing around I've found it's only an issue in routes but not components. Perhaps I'm misunderstanding how routes work (using marko-starter) but since the file names end with .marko I assume they're just components.
Not sure if this is the correct place for my issue anymore. Please let me know if there's a more appropriate place to open an issue.
ianvonholt
commented
6 years ago @austinkelleher I'm encountering this bug as well with anything after the hydrate update in lasso@2.11.22
Working versions:
lasso@2.11.21
lasso_marko@2.4.0
marko@4.7.4The error is quite simple, in my case:
events.js:183
throw er; // Unhandled 'error' event
^
Error: Render async fragment error (lasso-slot:head). Exception: Error: Async fragment (lasso-slot:head) timed out after 30000ms
at Timeout._onTimeout (.../node_modules/marko/dist/runtime/html/AsyncStream.js:190:33)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5)
at AsyncStream.error (.../node_modules/marko/dist/runtime/html/AsyncStream.js:426:13)
at Timeout.<anonymous> (.../node_modules/marko/dist/runtime/html/AsyncStream.js:190:27)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5)
App stopped unexpectedlyI'll see if I can't track down more of what is happening.
VSJ
commented
6 years ago @ianvonholt any update on this issue? I am facing the same problem.
slavik-m
commented
6 years ago +1 Guys.
ianvonholt
commented
6 years ago Sorry @VSJ, I haven't had time to investigate. Priorities at work shifted away from newer Marko and Lasso version support.
slavik-m
commented
6 years ago Try to update lasso to the new version manually.
Lasso version 3.1.3 works correctly.
This is a lasso-cli issue. Need to update the "lasso": "^2.11.19" dependencies on the lasso-cli package.
caracal7
commented
6 years ago I have the same issue(
jacobgoh101
commented
6 years ago I received this error in marko-starter.
The advice from this article works for me.
Just update
"dependencies": {
"marko": "^4.2.4",
"marko-starter": "^1.0.0"
},to
"dependencies": {
"marko": "^4.4.28",
"marko-starter": "^2.0.1"
},and rerun npm install.
7shabir
commented
5 years ago @jacobgoh101 Perfect! I've been looking for this solution for a long time.
Exception has occurred: Error Error: Render async fragment error (lasso-slot:body). Exception: Error: Async fragment (lasso-slot:body) timed out after 30000ms at Timeout._onTimeout (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/runtime/html/AsyncStream.js:193:32) at ontimeout (timers.js:386:14) at tryOnTimeout (timers.js:250:5) at Timer.listOnTimeout (timers.js:214:5) Creation stack trace: Error at AsyncStream.beginAsync (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/runtime/html/AsyncStream.js:188:55) at render (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/lasso/taglib/slot-tag.js:94:28) at render (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/lasso/taglib/body-tag.js:10:5) at wrappedRenderer (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/runtime/helpers.js:106:13) at render (/Users/sandeep/Desktop/web.sdk/sdk-revamp/src/components/app-main/index.marko.js:46:3) at renderer (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/components/renderer.js:186:9) at wrappedRenderer (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/runtime/helpers.js:106:13) at render (/Users/sandeep/Desktop/web.sdk/sdk-revamp/src/templates/product/index.marko.js:29:3) at renderer (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/components/renderer.js:186:9) at safeRender (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/runtime/renderable.js:6:9) at AsyncStream.error (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/runtime/html/AsyncStream.js:429:13) at Timeout._onTimeout (/Users/sandeep/Desktop/web.sdk/sdk-revamp/node_modules/marko/src/runtime/html/AsyncStream.js:193:26) at ontimeout (timers.js:386:14) at tryOnTimeout (timers.js:250:5) at Timer.listOnTimeout (timers.js:214:5)