Publishing is a nightmare
See original GitHub issueHey, please fix the publishing workflow.
It is very frustrating and confusing. Somehow I got 2 packages and 1 collection published, but I can not get the other 2 published and I have no idea why. (e.g. this one: https://github.com/nuclei/status-bar)
I have a bower.json, but when I try to publish it, the loading spinner just keeps spinning forever. Refreshing the page shows:
Error
Unable to process element
missing bower.json
I am sure there is a valid reason for this, but it is just not clear. The preview of my element works fine.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
My Publishing Nightmare – the story of a book deal gone bad ...
This is the story of how bad things happened to an author. Me, as it happens. I was naive, disorganised, and arguably lazy...
Read more >When Publishing Dreams Become a Nightmare
Most of my clients have had terrific publishing experiences. They enjoy working with their editors (even when the revisions are very ...
Read more >Publishing Is a Nightmare: 31 Horror Films about Writing ...
Publishing Is a Nightmare : 31 Horror Films about Writing, Reading, and the Book Business. Fill your October with the horrors of literature....
Read more >Publishing Is a Nightmare on Apple Books
Yes, you can make money self-publishing books. ... Publishing Is a Nightmare ... of hardworking dropshippers, publishers, and more honest competitors.
Read more >A Publishing Nightmare - IBPAIBPA - IBPA Independent
A Publishing Nightmare ... Chicago Review Press recently published a title called Cuba and Its Music (clothbound, 600 pages, $36) to rave reviews...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For now only site admins can delete. But, publishing a brand new version should be sufficient to kick everything off again.
Yeah, we definitely want to improve the error messages. In this case linking directly to where we expected to find the
bower.json
file would probably have helped track down where this was going wrong. Let’s keep this issue open until we have at least that much.#879 should help, although not exactly linking directly to where we expected to find the file. I’m going to close this issue as fixed. If you spot more issues, let me know!