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

🐛 BUG: "Failed to resolve entry for package" for the Astro Component template #3049

Closed
1 task
markteekman opened this issue Apr 9, 2022 · 4 comments · Fixed by #3137
Closed
1 task
Assignees

Comments

@markteekman
Copy link
Contributor

What version of astro are you using?

1.0.0-beta.5

What package manager are you using?

npm

What operating system are you using?

Mac

Describe the Bug

Installing the Astro Component template produces an error while trying to run the development command:

# Initialize the Astro Component template in a new directory
npm init astro my-new-component-directory -- --template component

Schermafbeelding 2022-04-09 om 10 40 20

I made a StackBlitz example using astro.new which ran the command automatically after installing the dependencies and it showed the error right away.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-nzbssy?file=README.md

Participation

  • I am willing to submit a pull request for this issue.
@JustinyAhin
Copy link

Hello @markteekman. I'm also encountering the same issue.

Have you been able to fix it?

@markteekman
Copy link
Contributor Author

Hey @JustinyAhin, no I haven't been able to fix it. For the moment I'm still using my old setup, which is a demo project where I build and test the components before including them in the actual package 🙂

@preetamslot
Copy link

Got the same error, it looks like if you get an error in your code, in my case it was a wrong tailwind class in Vue , this is the error you get. looks like the error trace is broken :(

@bholmesdev
Copy link
Contributor

bholmesdev commented Apr 18, 2022

I've been noticing this error log overriding quite a few useful error logs. I suspect some of our error log changes may have caused this to surface. Trust me, it makes the core team's job much tougher as well 😆 Working on a fix!

@bholmesdev bholmesdev self-assigned this Apr 18, 2022
🐛 Bug Tracker automation moved this from Needs Triage to Done Apr 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants