Skip to content

Import example in docs has incorrect node module path #240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mgwedd opened this issue Apr 5, 2021 · 2 comments
Open

Import example in docs has incorrect node module path #240

mgwedd opened this issue Apr 5, 2021 · 2 comments

Comments

@mgwedd
Copy link

mgwedd commented Apr 5, 2021

The README instructions suggest importing the module as follows:

import SegmentedControl from '@react-native-segmented-control/segmented-control';

However, the package is installed under @react-native-community/segmented-control, not @react-native-segmented-control/segmented-control

Suggested change:
import SegmentedControl from '@react-native-segmented-control/segmented-control';
Should be changed to:
import SegmentedControl from '@react-native-community/segmented-control';

Using React Native v0.63.3, Node JS v12.19.0and NPMv7.7.6`

@mmehmetAliIzci
Copy link
Contributor

mmehmetAliIzci commented Jun 7, 2021

Hi @mgwedd
I believe the problem resides in the following:

There is two packages published in npm.
image

"@react-native-community/segmented-control",
"@react-native-segmented-control/segmented-control"

Both of them points to the same repository. Hence the problem with the Readme. I would love to help about this if you need this @Naturalclar. But I believe this is a credential sensitive topic. Is there a reason why we have 2 separate npm entries for this package ?

I also see that this one is version wise ahead from the "@react-native-community/segmented-control" community one. I would expect these kind of misalignments.

Mehmet

@Naturalclar
Copy link
Member

Hello! Sorry for the confusion.
We're in the middle of migrating packages out of the @react-native-community namespace, hence the multiple name space for this repo.
More details can be found here
react-native-community/discussions-and-proposals#330

Please migrate to the new namespace whenever possible, as the old namespace wont be maintained from here on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants