Some links on the homepage do not exist about cdnjs HOT 2 CLOSED

Great pickup @vierbergenlars! I've fixed all of the issues you brought up, but moving forward I think we should have a process to prevent this from happening again.

I think a shell script that checks all package.json's produce a valid path as determined by our path construction function. What do you think?

from cdnjs.

I don't know much about shell scripts, but I don't think it can easily be added to packages.json.sh, it is difficult to decode JSON with a shell script.

I can think of 3 other possibilities:

• Use awk to add another parameter to each package.json file with the correct path
• Or use Python or Ruby to decode the package.json string, add an extra parameter to it if the path doesn't match and encode it back.
• But the easiest solution may be to ask the authors of a script to add a "displayName" parameter to use another name in the script's title on cdnjs.

from cdnjs.