-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
not possible to add external link #4
Comments
Does this refer to the issue of not being able to reference anything outside of the folder defined for .root? Such as linking to a script installed via "npm install --save package" in the node_modules folder? If that's what you're referring to: A potential solution after looking at the code might be to keep the root always as the root. What the user adds to the root actually get's added in front of the import strings. Then for vulcanize add excludes as an option to the other folders via regexp except for node_modules folder since it seems like the build process is painstakingly low (trying this approach without excludes right now but it's been building for quite some time, probably since vulcanize goes over the entire project) |
@AndreasGalster mwc:ecmascript is also a possible suspect since it goes through every script(with size < 100 by default) thats there inside the vulcanized html. Try logging mwc:ecmascript and see if any script is delaying the build time. |
...
"mwc:ecmascript@1.0.10": {
"limit":true,
"log":true
}
... |
@AndreasGalster you can find the log file inside .mwclogs folder |
create a html file in meteor client folder & refer meteor public folder link inside that
The text was updated successfully, but these errors were encountered: