mantine icon indicating copy to clipboard operation
mantine copied to clipboard

Spotlight renders out to the left of the screen in Production using Remix (express server)

Open ihpannu opened this issue 3 years ago • 14 comments

What package has an issue

@mantine/spotlight

Describe the bug

Spotlight renders out to the left of the screen in Production using Remix (express server). Works perfectly well using in Dev environment. I had the same issue with modals but solved using within portal props and facing problems on the latest @remix and "@mantine/hooks": "^5.1.5",

Please suggest

What version of @mantine/hooks page do you have in package.json?

5.1.5

If possible, please include a link to a codesandbox with the reproduced problem

No response

Do you know how to fix the issue

No

Are you willing to participate in fixing this issue and create a pull request with the fix

No

Possible fix

No response

ihpannu avatar Aug 14 '22 01:08 ihpannu

Hi @ihpannu, you can set withinPortal prop on SpotlightProvider the same way as on Modal component. If that does not help, please provide a repository with minimal reproduction, use mantine remix template as base for your repository.

rtivital avatar Aug 14 '22 07:08 rtivital

-I will submit today also having few other issues such as

  • rightSection icon in input renders out of the box on initial page load
  • 404 doesn't render styles. After a refresh styles load back.
  • Spotlight renders under the navbar to the left

Attached some screenshots for now will push an repo to show live results image image

ihpannu avatar Aug 17 '22 03:08 ihpannu

@ihpannu are you using mantine-remix-template?

rtivital avatar Aug 17 '22 05:08 rtivital

@rtivital Yes this started happening since I switched to mantine 5 and react 18 using the template provided on the website

ihpannu avatar Aug 17 '22 15:08 ihpannu

@rtivital another example of spotlight it's still in the dom tree image

ihpannu avatar Aug 17 '22 16:08 ihpannu

React 18 is not supported with Remix template, downgrade to react 17 to solve these issues.

rtivital avatar Aug 17 '22 16:08 rtivital

@rtivital Rolled back to React 17 and Mantine 5.1.6 all same issues still persist. This app is running in production on Railway using remix/express server

ihpannu avatar Aug 17 '22 18:08 ihpannu

Well, I cannot help much, if you can reproduce an issue in mantine-remix-template and send the repo I can have a look

rtivital avatar Aug 17 '22 18:08 rtivital

@rtivital attached is the link to the repo using mantine-remix-template on GitHub https://github.com/ihpannu/mantine-remix-template and link to the live site reproducing the error https://mantine-remix-template-production.up.railway.app/

ihpannu avatar Aug 17 '22 18:08 ihpannu

React 18 is not supported with Remix template, downgrade to react 17 to solve these issues.

Is supporting React 18 w/ Remix on the roadmap?

andremonteiro95 avatar Aug 21 '22 16:08 andremonteiro95

In a long term – maybe, in short term – no. With current remix direction (server streaming as default) I doubt that it will worth the effort to support remix at all. As for current state – remix feels very unstable – we've already had to change ssr logic twice in the past 6 months, so I'm not planning to work on it any time soon until remix becomes at least a little more mature (in terms of css-in-js handling).

rtivital avatar Aug 21 '22 17:08 rtivital

@rtivital do you recommend porting over to Next.js? we cannot afford to change the UI lib at the moment and given the mantine/remix plan it doesn't seem ideal to continue using the broken framework on the production level

ihpannu avatar Aug 22 '22 01:08 ihpannu

Well, it's up to you, I have several next.js app running in production without any issues built with Mantine.

rtivital avatar Aug 22 '22 06:08 rtivital

@rtivital Thank you for advice

ihpannu avatar Aug 22 '22 07:08 ihpannu

Possibly related to https://github.com/mantinedev/mantine/issues/2311

alukach avatar Oct 21 '22 17:10 alukach

This issue is closed for one of these reasons:

  • It was fixed in 7.0
  • It is no longer reproducible in 7.0
  • It is no longer applicable in 7.0
  • It does not have a reproduction

If you think that this issue was closed by mistake, and it is still an issue in version 7.0, please reopen it.

rtivital avatar Sep 19 '23 06:09 rtivital