https://github.com/charlesread/lasso-marko-bundle-issue

Shows a small bug in lasso-marko and how it bundles stuff in components
https://github.com/charlesread/lasso-marko-bundle-issue

Last synced: about 2 months ago
JSON representation

Shows a small bug in lasso-marko and how it bundles stuff in components

• Host: GitHub
• URL: https://github.com/charlesread/lasso-marko-bundle-issue
• Owner: charlesread
• Created: 2017-04-11T13:22:38.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2017-04-11T13:57:04.000Z (over 7 years ago)
• Last Synced: 2024-10-17T14:54:50.711Z (2 months ago)
• Language: JavaScript
• Size: 2.93 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
This is a simple demonstration of what I believe to be a small bug in either `lasso 2.11.8`, `marko 4.2.7`, or `lasso-marko 2.3.0`, but probably `lasso-marko 2.3.0`.

When one attempts to have a supplementary Javascript file bundled in a `marko` component, by referencing it in `browser.json`, `lasso`/`lasso-marko` does not bundle the supplementary Javascript file _unless_ there is a `[*_]component.js` file in the component's folder.

This project uses `Hapi` to serve a page rendered and bundled by `marko` and `lasso`, you can see the issue by:

`npm install`

`node index.js`

Then just browse to [http://localhost:8000](http://localhost:8000), notice that the file `components/broken-component/lib.js` does not get bundled (it contains an `alert` so you can tell that it's not being bundled just by visiting the page).