npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ray-js/code-sandbox

v0.0.4

Published

小程序 CodeSandbox 容器

Downloads

326

Readme

English | 简体中文

@ray-js/code-sandbox

latest download

CodeSandBox container

Installation

$ npm install @ray-js/code-sandbox
# or
$ yarn add @ray-js/code-sandbox

Develop

# watch compile component code
yarn watch
# watch compile demo
yarn start:tuya

Usage

Mini -program docking

Must -dependencies in installation

yarn add @ray-js/code-sandbox @ray-js/ray

Create a new Playground page in the PAGES directory, the content is as follows

import React from 'react';
import CodeSandbox from '@ray-js/code-sandbox';

import * as RayComponents from '@ray-js/ray';

export default function Home() {
  return (
    <CodeSandbox
      defaultTitle="CodeSandbox"
      context={{
        // The three -party library of Import from in CODESANDBOX
        '@ray-js/ray': RayComponents,
      }}
    />
  );
}

Page index.config Configuration Custom Topbar

export default {
  navigationStyle: 'custom',
};

Platform docking

Must -dependencies in installation

yarn add @ray-js/code-sandbox antd axios styled-components lodash @saber2pr/monaco

Method 1: Introduce Codesandbox editor to the page:

import { CodeSandboxButton } from '@ray-js/code-sandbox/lib/txp'

<CodeSandboxButton
  title="Playground" // The title of Editor's pop -up window
  code={`
import { Button } from '@ray-js/smartui';

export default function Demo() {
return <Button>测试</Button>
}

`}
  txpCode="SmartUi" // Fill in the component Code on TXP here
  pageName="playground" // The page name of the CodeSandBox component is introduced in the applet project, such as Pages/Playground/Index, and Pagename is Playgroundd
/>

After clicking the button, you will pop up the window to open the CodesandBox editor

Method 2: Do not use the button pop -up window, directly access the editor+simulator:

import { CodeSandbox } from '@ray-js/code-sandbox/lib/txp'

  <CodeSandbox
    title="Button 组件" // The title in DEMO container
    code={`
import { Button } from '@ray-js/smartui';

export default function Demo() {
  return <Button>测试</Button>
}

`}
    txpCode="SmartUi" // Fill in the component Code on TXP here
    pageName="playground" // The page name of the CodeSandBox component is introduced in the applet project, such as Pages/Playground/Index, and Pagename is Playgroundd
  />

Notice

  1. The components specified by TXPCODE need to be built through CI DEMO on the TXP platform before they can be connected to the Codesandbox simulator.

  2. The resources and component DEMO containers involved in the editor have been uploaded to the graffiti CDN, which can be used in external projects.

  3. Most Basekit capabilities in the simulator support, some device -related TTT methods do not support it.