ahmadnassri / node-metalsmith-paths Goto Github PK

This completely broke our metalsmith build. Luckily I had a link checker that caught it.

See the test change here:
f5eb149#diff-910eb6f57886ca16c136101fb1699231R24

Hello!

On windows, there is a problem with directory string because contains backslash instead of forward slash.
Error example:
paths.dir maindir\subdir
paths.href /maindir\subdir/index.html
paths.dhref /maindir\subdir/

It should be:
paths.dir maindir/subdir
paths.href /maindir/subdir/index.html
paths.dhref /maindir/subdir/

Hi there,

Thank you for this plugin. I've tried to use it but it seems to conflict with metalsmith-permalinks.

Unless I'm missing something, both seem to use the path property, so the path gets overwritten when the paths plugin runs before the permalinks plugin.

Can you confirm this issue? If so, would it make sense to rename the property to avoid the conflict? I'm using this method as a workaround on my local version, but it would be nice to do it in the repository.

With the directoryIndex pull request added, could we please update the version number to 2.1.2?

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:angularmaterial). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Cannot push to the Git repository.

semantic-release cannot push the version tag to the branch master on the remote Git repository with URL https://github.com/ahmadnassri/node-metalsmith-paths.git.

This can be caused by:

• a misconfiguration of the repositoryUrl option
• the repository being unavailable
• or missing push permission for the user configured via the Git credentials on your CI environment

Good luck with your project ✨

Your semantic-release bot 📦🚀