Skip to content
#

preact

Here are 1,485 public repositories matching this topic...

Strange-AI
Strange-AI commented Sep 18, 2018

JS 配置如下:

 var gitalk = new Gitalk({
            clientID: '3654916*****0c0038c28',
            clientSecret: 'd90d031a*****0e0fa4c7fe2fae747b96b',
            repo: 'Strange-AI.github.io',
            owner: 'Strange-AI',
            admin: ['jinfagang', 'Strange-AI'],
            id: vm.codeId,
            distractionFreeMode: false
        });
        gitalk.render('gitalk-conta
marvinhagemeister
marvinhagemeister commented Oct 20, 2020

Just came across one of our client projects, which uses their own npm registry instead of the official one. By making it configurable via cli-flag like --registry https://my-registry.com we could support that use case.

I'm wondering if this is how we can make our npm plugin testable too! We could spin up a fake registry since we only ever download the tarball and use the --registry flag in

enhancement help wanted good first issue reliability
tsparticles
matteobruni
matteobruni commented Apr 27, 2022

Version 2.x introduced a lot of new packages, almost every feature has a plugin package now but the component packages have some different versions and names.

Since I'd like to have the same version for the whole project, and a better naming, all packages, except "tsparticles" will be moved to the @tsparticles\ npm group.

This is what is going to be with version 3:

`tsparticles-engine

documentation enhancement help wanted good first issue

Improve this page

Add a description, image, and links to the preact topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the preact topic, visit your repo's landing page and select "manage topics."

Learn more