Gathering detailed insights and metrics for codesandboxer-fs
Gathering detailed insights and metrics for codesandboxer-fs
npm install codesandboxer-fs
Typescript
Module System
Node Version
NPM Version
67.2
Supply Chain
80.8
Quality
73.7
Maintenance
50
Vulnerability
99.3
License
JavaScript (90.43%)
CSS (4.19%)
HTML (3.12%)
Vue (1.69%)
TypeScript (0.42%)
SCSS (0.08%)
Sass (0.07%)
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Total Downloads
3,772,510
Last Day
380
Last Week
1,803
Last Month
8,932
Last Year
125,151
MIT License
540 Stars
179 Commits
73 Forks
13 Watchers
8 Branches
13 Contributors
Updated on Feb 27, 2025
Minified
Minified + Gzipped
Latest Version
1.0.3
Package Id
codesandboxer-fs@1.0.3
Size
6.93 kB
NPM Version
6.2.0
Node Version
10.9.0
Published on
Jul 15, 2019
Cumulative downloads
Total Downloads
Last Day
8.3%
380
Compared to previous day
Last Week
3%
1,803
Compared to previous week
Last Month
38.4%
8,932
Compared to previous month
Last Year
-16.2%
125,151
Compared to previous year
4
1
Deploy a single javascript file to codesandbox as a react entry point, bundling up other files you need, as well as the relevant dependencies, using codesandboxer
's default package under the hood to bundle files.
$ yarn global add codesandboxer-fs
or
$ npm i -g codesandboxer-fs
$ codesandboxer some/file/path.js
This will take this file, upload it and its dependent files to codesandbox, and assume that the file passed in is a renderable react component. It will also bundle any needed dependencies from your package.json
The response will look something like
1{ 2 "sandboxId": "481nzy3v84", 3 "sandboxUrl": "https://codesandbox.io/s/481nzy3v84?module=/example" 4}
which will be printed to your console.
codesandboxer-fs
uses the context of the package the target file is from, bases its available npm dependencies on that file's package.json
, and will not include files imported from places outside this scope.
If you point at a file with an extension that is not '.js', that file type will be loaded using our '.js' logic. This is to allow extensions such as '.jsx'.
--dry -d
- this flag bundles the files, and prints them to the console, as well as the list of files to be sent to codesandbox.
--name -n
- this flag names the created sandbox, making the base link more informative when shared.
allowedExtensions - this flag provides additional extensions that will be accepted. Note that the extension type of your target file is automatically added. The format is .jsx,.ts
, a comma separated list of file types.
--template -t
- a string of what template to use in sending files to codesandbox. Current officially supported templates are react
and react-typescript
.
The codesandbox CLI is intended to upload an entire create-react-app project, and as such is not designed to cherry-pick a file. Codesandboxer's goal is fundamentally different, in that it wants to focus on a single component, such as an example. Codesandboxer is going to be more useful if you want to share proposed changes to a component within an existing project with someone, while codesandbox will be better for uploading and looking at an entire website.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
branch protection is not maximal on development and all release branches
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 1/11 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
56 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-02-24
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More