Replace Laravel Mix with Bud

[kellymears]

No description provided.

[QWp6t]

It looks like Tailwind isn't working correctly. The configured classes aren't being included during compile, but all of the @apply stuff is.

I have confirmed that tailwind.config.js is loading during compile.

screenshots

[kellymears]

@QWp6t I think this is almost 100% good to go. I don't think the base path is being set properly for relative css imports, but proxy/hmr/postcss/react all seem to be on their best behavior. File hashing works well, minification works well. It feels fast.

I will need to also try dropping some actual production dependencies. Out-of-the-box there is no runtime/vendor bundle generated as there are no deps to bundle.

• Fix base path for relative urls in css
• Confirm runtime / vendor bundles are correctly generated
• Fix CI

[Jamiewarb]

Just chatting with Ben about this, and wanted to reach out and see if there's anything a potential contributor could help with for this to help get it over the line. Let me know if there's anything I can do to help ☺️

[knowler]

Suggested change

	export const domReady = (onReady) => {
	window.requestAnimationFrame(function check() {
	document.body ? onReady() : window.requestAnimationFrame(check);
	});
	};
	export const domReady = (onReady) => {
	window.requestAnimationFrame(document.body ? onReady : domReady);
	}

We can check for the body immediately, right? Do we even need to do that in an animation frame the first time it’s called? I don’t know enough about window.requestAnimationFrame, so I could be wrong. (I am wrong, the falsy passed domReady in my suggestion loses the reference to onReady.)

As an aside, I think we should change the name of this function to bodyIsReady (alternatively prefixed with my), since it kind of breaks the mold of DOM readiness functions (particularly by going outside of the definition of DOMContentLoaded).