Skip to content
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

Local development server unable to find custom components #59

Closed
morwalz opened this issue Apr 23, 2020 · 10 comments
Closed

Local development server unable to find custom components #59

morwalz opened this issue Apr 23, 2020 · 10 comments

Comments

@morwalz
Copy link

morwalz commented Apr 23, 2020

sfdx-project.json

{ "packageDirectories": [ { "path": "xyz", "default": true } ], "namespace": "xyz", "sfdcLoginUrl": "https://login.salesforce.com", "sourceApiVersion": "45.0" }
I am trying to use component from same package.
<c-component-from-same-package></c-component-from-same-package>
and functions from same package

import { getContactsRequiredFields, proxyObjectConverter, setOrgChartContacts } from "c/utility"; show errors unable to find the file or component.
When i change c to package name then local development server work but i can not push the code to org as there is rule which only allow component with c-

@stale
Copy link

stale bot commented Apr 30, 2020

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

@stale stale bot added the type:bug-p3 label Apr 30, 2020
@morwalz
Copy link
Author

morwalz commented May 4, 2020

Anyone can help here ??
it is very critical to us.

@stale stale bot removed the type:bug-p3 label May 4, 2020
@mysticflute
Copy link
Contributor

@morwalz are your LWC components located under xyz/main/default/lwc? Also do you have a localdevserver.config.json file specified?

@morwalz
Copy link
Author

morwalz commented May 8, 2020

Hi @mysticflute Yes, my LWC components are defined under xyz/main/default/lwc folder.

And i have created localdevserver.config.json file. In this file I have added namespace as well.

@stale
Copy link

stale bot commented May 15, 2020

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

@stale stale bot added the type:bug-p3 label May 15, 2020
@git2gus
Copy link

git2gus bot commented May 15, 2020

This issue has been linked to a new work item: W-7571627

@morwalz
Copy link
Author

morwalz commented May 15, 2020

How can i see this what is mentioned in the work item ?

@stale stale bot removed the type:bug-p3 label May 15, 2020
@stale
Copy link

stale bot commented May 22, 2020

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

@stale stale bot added the type:bug-p3 label May 22, 2020
@git2gus
Copy link

git2gus bot commented May 22, 2020

This issue has been linked to a new work item: W-7606242

@lcampos
Copy link
Contributor

lcampos commented Jul 9, 2020

Release 2.4.0 addresses this limitation. Thanks for opening this issue and providing feedback.

@lcampos lcampos closed this as completed Jul 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants