Some dependencies for demo pages give http status 400
See original GitHub issueHello,
I’ve an element that works properly using polymer serve
, howerver on webcomponents org some files are not being served to the client and end up with http status 400.
https://www.webcomponents.org/element/polymer-ui-router/demo/demo/index.html
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Status Code 400 (Bad Request) Explained & How to fix it - Ryte
A HyperText Transfer Protocol Bad Request 400 indicates a client error. When the client sends an invalid request to the server, the server...
Read more >Bad request error 400 when publishing to npm packages
Hi everyone, I'm new here and am trying to publish a test package on my gitlab registry but for some reason I can't...
Read more >HTTP Status Codes: All 63 explained - including FAQ & Video
HTTP status codes are three-digit responses from the server to the browser-side request. Everyone has probably gotten the classic 404 page-not-found error.
Read more >400 Bad Request - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 400 Bad Request response status code indicates that the server cannot or will not process the request ...
Read more >HTTP Status Codes List | HTTP Error Codes Explained
Read about the HTTP status codes and their descriptions. ... the 400 status code error and header information, the server can provide additional...
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
@LostInBrittany: thanks for all that.
I was already aware of the problem and had come to the same conclusions about how to resolve this. Unfortunately, it took me a while to implement running into lots of issues, but #1220 should address this. I tested manually with your broken package (2.1.2) and it works. However, it is pretty slow simply because generating the
package-lock.json
can take some time depending on the package we’re installing. The fact thatdevDependencies
are needed aggravates this issue.You can try it out but you may see faster results since generation may be cached.
That’s great, @samuelli !!! Thanks again!