New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOCS: It's not clear where to execute code to register lasso-marko plugin #1109
Comments
LassoJS is not MarkoJS. The document page is pretty informative with that in mind, has the proper configuration example for LassoJS, and even includes links back to the LassoJS github repo. Is there something that is not particularly clear? Deeper dive of what is happening: To bundle MarkoJS pages together, utilizing LassoJS, you need to include the appropriate Lasso plugins in your Head over to https://github.com/lasso-js/lasso on how to utilize the bundler with a configuration file. Example: lasso-configure.js
You'll then need to configure your lasso context in some form as your server starts up:
|
It's super clear that lasso is one of many bundlers which you can use for marko. But that's not my point. My point is exactly the last snippet in your answer.
Exactly that information is missing in the docs. You need to only for server side rendering, right? But in my case, I don't don't want to do that during server start up time, imagine I don't even start a server, so what do I need to do then? BTW: the API is a bit weird, to have a side effect using |
Docs/examples have been updated! |
Marko Version: 4.12.4
It's not clear where to execute the code snippet to register lasso-marko plugin
Details
See https://github.com/marko-js/marko/blame/168dc9b71e60a442a559faea09f940e00c80fb51/docs/lasso.md#L15-L24
So, it's about this snippet
Expected Behavior
See in which context (which file, like the other snippets) the snippets needs to exist or where to run it from.
Actual Behavior
No context given, just a code snippet.
Possible Fix
Tell the user where to put the snippet
The text was updated successfully, but these errors were encountered: