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

package.json name influences build #7375

Open
jcbvm opened this issue Oct 11, 2017 · 2 comments
Open

package.json name influences build #7375

jcbvm opened this issue Oct 11, 2017 · 2 comments

Comments

@jcbvm
Copy link

jcbvm commented Oct 11, 2017

I ran into an issue where my assets could not be loaded.
It turns out that my project had @scope/project as name in package.json, which caused the build to prepend @scope to the assets, this seems broken to me because having a namespace is certainly valid for json packages.

@rwjblue
Copy link
Member

rwjblue commented Oct 11, 2017

Would you mind putting together a demo that would help us understand the setup you are describing?

@jcbvm
Copy link
Author

jcbvm commented Oct 12, 2017

I've created a sample app at https://github.com/jcbvm/ember-cli-example
In package.json the name of the project is prefixed with a scope (@jcbvm), when I run ember s, resources are put in a new directory in the assets folder. I've pushed the dist folder, so you can see a folder called @jcbvm in the assets folder. Because of this folder, resources can not be find when viewing the app in the browser.

@locks locks added this to Needs Team in Triaging Jan 10, 2022
@locks locks moved this from Needs Team to Needs Confirmation in Triaging Jan 10, 2022
@locks locks moved this from Needs Confirmation to INBOX in Triaging Jan 20, 2022
@locks locks moved this from INBOX to Needs Reproduction in Triaging Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Triaging
Needs Reproduction
Development

No branches or pull requests

4 participants