Spanish localization done and merged, but not published to NPM registry? (missing package contents?)
See original GitHub issueMerged PR: https://github.com/dequelabs/axe-core/pull/1758
Spanish locale exists in codebase at release tag3.3.2
:
https://github.com/dequelabs/axe-core/tree/v3.3.2/locales
…but does not exist in published NPM package: https://unpkg.com/browse/axe-core@3.3.2/locales/
CC @nvdaes
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Package is not publishing to npm (not in the npm registry)
Try npm login . In case of npm publish , sometimes misleading message is shown.
Read more >npm packages in the Package Registry - GitLab Docs
Watch a video demo of how to publish npm packages to the GitLab Package Registry. Publish to GitLab Package Registry. Authentication to the...
Read more >npm-publish - npm Docs
Description. Publishes a package to the registry so that it can be installed by name. By default npm will publish to the public...
Read more >Best practices for creating a modern npm package - Snyk
You will first learn how to create an npm package, so you can get familiar with building and publishing a package to the...
Read more >Workspace npm dependencies - Angular
The Angular Framework, Angular CLI, and components used by Angular applications are packaged as npm packages and distributed using the npm registry.
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 Free
Top 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
Spanish localization is now published in npm. So, I will close this issue. Thanks for your work!
@danielweck , you can close the issue and use this release for ACE.