Skip to content
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

experimental version #25

Closed

Conversation

jmikedupont2
Copy link

this is to test the patch

@Anush008
Copy link
Owner

How about we try the official release Tokenizers library?
I wouldn't do hot fixes for a public package.

@jmikedupont2
Copy link
Author

i am just trying to test this, you can disregard

@Anush008
Copy link
Owner

Got it. Thanks.

@jmikedupont2
Copy link
Author

I would love if you can test and release until then i am trying to load from git

mike dupont added 4 commits January 14, 2025 06:01
This step is to remove the need to publish to npm,
the idea is that each module can be build as a docker file and then
linked into where it is needed to compose new runtimes with only the
needed modules.

we can go further to separate the running of the code in a new
container later and pipe the data between containers or even across servers.
@jmikedupont2
Copy link
Author

i am working here on a new way to build and link the package via docker

@jmikedupont2
Copy link
Author

closing to avoid noise, if people need this they will find me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants