forcedotcom / lwc-dev-server-feedback

LWC Local Development
BSD 3-Clause "New" or "Revised" License
45 stars 10 forks source link

Local development server unable to find custom components #59

Closed morwalz closed 4 years ago

morwalz commented 4 years ago

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[bot] commented 4 years ago

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

morwalz commented 4 years ago

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

mysticflute commented 4 years ago

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

morwalz commented 4 years ago

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[bot] commented 4 years ago

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

git2gus[bot] commented 4 years ago

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

morwalz commented 4 years ago

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

stale[bot] commented 4 years ago

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

git2gus[bot] commented 4 years ago

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

lcampos commented 4 years ago

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