First of all congrats to your hopefully promising Product - BUT

Elements Feedback
1

RapidWeaver Elements 1.4.1 (23894)
We have been working intensively for almost two weeks to migrate an existing one-pager Tailwind website to Elements. The main challenge we are facing is embedding our own Webpack build. After considerable effort, it runs—but the system frequently hangs. When we reopen Elements, the Webpack instance still appears in the list, but it has been removed from the page and must be reinstalled. Once reinstalled, it works only for a short time (usually a day) before the issue repeats.

At this point, we have classified the product as unstable/buggy and are now relying on a fast, efficient bug-fixing process and culture to address these problems.

Best

1 Like
2

So correct me if I sm wrong you have a webpack written in Tailwind, which is causing Elements not to behave? Yet your saying Elements is is unstable snd buggy? Yet have you considered it’s your webapck that is the “fault” here. Sadly there are Tailwind codes that dont work in Eleemnets with tweaking them we.g. Codepen items cause problems but can be addressed. Why dont you put your code into a private session with @elementsbot and see whether the bot can give you some indications of what might be wrong?

1 Like
3

Hey there, JeanLuc! So it seems your Webpack adventure in Elements has turned into a bit of drama. Let’s unravel this knot, shall we?

First up, PMUK’s got a point—embedding stuff like Webpack can be a bit of a fiddle, especially when things go poof after a while. Elements and Tailwind play nice, but it’s crucial to ensure your Webpack bundle is friendly with Elements’ environment.

Before we get too ahead of ourselves, could you try these tidbits:

  1. Check Versions: Ensure your Tailwind and Webpack builds are compatible with the latest versions used in Elements.

  2. Isolate Issues: See if a simpler version of your build without complex dependencies works. Sometimes, a barebones approach helps locate the troublemaker.

  3. Seek Logs: Dig into any logs for sneaky error messages when Elements hangs. They could be littered with clues.

  4. Reinforce with Updates: Make sure Elements is up-to-date—sometimes, the freshest bits work wonders.

If you’re still head-scratching after these, let’s have a deep dive into your specific code setup. You can pop details of your Webpack and Tailwind configurations here, and yours truly will flutter around with some virtual magic. :glowing_star:

Remember, Elements is as dynamic as you and might have little quirks, but working those out is what we’re here for!