-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider publishing to https://packagist.org/ #16
Comments
The package used to be on packagist i'm correct. https://www.tawk.to/knowledgebase/plugins-and-modules/magento-2-integration/ |
Hmm, might have been a mistake in their documentation then, but at this moment it's not on there: https://packagist.org/search/?q=tawk%2Fwidget |
@alvinjohnsonso could you do this? Do not forget to setup the webhook on the repository. the guide how to will be displayed after setup the packagist package. Thank you in advance! |
We are still waiting) |
+1 the request. The guidance from README for adding source vsc is a setback, consider to add tawk/url-utils also |
Hello everyone, Thank you for your feedback and suggestions. We will be publishing on Packagist soon. We noticed an issue with our package name To ensure that existing installations continue to work as expected, we have decided to move our development to a new fork and archive this repository. The package will be published from the new fork, and all future releases will be launched from there. |
@eug-L: is this the new fork: https://github.com/tawk/tawk-magento-2-package ? |
@hostep that is correct |
Perfect! Thanks for the effort, also for keeping the exact same old versions published in the new module. I moved 2 of our projects to the new package with their original version and found no changes in the source code, which is much appreciated! |
Hi guys
Could you consider to publish your package to https://packagist.org/ ?
That way there are fewer steps to take to install the module and we don't need to configure an extra repository in our
composer.json
file.Thanks!
The text was updated successfully, but these errors were encountered: