If you use both multiple and slim on your <portal-target>, only the first <portal> to send content to the <portal-target> gets to have its content rendered. Here's a reproduction link:
https://codesandbox.io/embed/portal-vue-multiple-slim-rdhet

Issue

16 files has some sort of Sugar Pro references in code as comments.
Those should be removed

Steps to Reproduce

Try the search with BEGIN: pro
https://github.com/salesagility/SuiteCRM/search?q

Naively I set <Portal node={document.body} >... and it breaks with react 15 (works with 16).
When I say break, I mean that the portal content is replacing the body instead of appending to it.

Until I figured out that I can simply omit the node prop, and use react-portal's default behaviour.

I just thought this is something that might either require special code handling,
or at least a

It's not showing spinner as well in the react-native version 0.62.
Not sure about the reason.
facebook/react-native#28098
similar with this issue?

Just a suggestion based upon a gotcha I encountered. When using SSR you get 'document is not defined' (since document is client side only). I modified your example to remedy this.

  const { Portal } = usePortal({
    bindTo: typeof window !== 'undefined' ? document && document.getElementById('selector') : null
  })

Thanks for the package.

Suggestion to improve documentations

Description

I have a thought and want to share. More like a personal opinion.
I've found it difficult to navigate through Piral documentations.

Piral Team has done an amazing job and documenting everything which makes getting started with Piral easy. Though on a day-to-day basis, I find myself needing to refer to the doc often... and struggling to

Please note that webpack-dev-server is presently in a maintenance-only mode and will not be accepting any additional features in the near term. Most new feature requests can be accomplished with Express middleware; please look into using the before and after hooks in the documentation.

For reference https://github.com/webpack/webpack-dev-server

Mostly I created this issue because I want to h

Actual behavior

would it be possible to have a synthesis of the documentation to understand something ?

how to monitor the connections, possible bypass of the system?
how to recover regulatory logs in France?
how does all this work?

I intend to do a doc for memory, she can serve to other (on the Wiki ?)

Thanks

The test coverage of PlanetApplicationLoader is 70.55%
https://coveralls.io/builds/29067505/source?filename=packages/planet/src/application/planet-application-loader.ts#L35

This master issue contains a list of Renovate updates and their statuses.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• chore(deps): update apache pluto to v3 (major) (org.apache.portals.pluto:pluto-container, `org.apache.portals.plu

Not sure if it's on our side or on leaflet one but it's annoying, to be verified on other use case, happens with /fr/admin/dataset/57f0b8f088ee3808545ff490/ for instance.

androi 5.1, chrome

Cái menu này trượt ra thì dễ mà lúc truợt vào không dùng tay trượt được. Cũng không có nút để đóng. Nên xem lại chứ thế này làm khó người dùng.

• Size and fearture comparison with portal-vue
• interactive example(s)

Please add to README.md, some information for babel-preset-react-union. For me wasn't intuitive to instantly look into /packages. From .babelrc file it's to much magic behind it.
And also https://www.npmjs.com/package/babel-preset-react-union doesn't contain any description (README).