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 🙏

© 2026 – Pkg Stats / Ryan Hefner

fcs-core-viewer

v0.62.0

Published

3D Viewer in the Cloud

Downloads

453

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

femsolve-kftfemsolve-kft

Keywords

Readme

Viewer3D/Editor3D Packages

Native mesher selection (Editor3D)

Editor3D sends meshing requests to ModelService; browser code does not load GMSH/Netgen DLLs. Static Viewer3D only visualizes the resulting geometry/mesh.

  • Existing face presets retain their routing: QuadDominated selects Netgen; this is not a new global main-engine setting.
  • The volume tool has a GMSH / Netgen selector. OpMeshVolume.ts sends boolean usegmsh for preview and accept; omitted selection defaults true for backward compatibility.
  • ModelService3200 propagates selection to Engine Mesh3DSettings. Source-built GMSH remains the default; native Netgen uses Engine/PyAPI, not pip Netgen.
  • Netgen volumes require a closed, consistently oriented linear triangular boundary and produce TET4/TET10. Quad/quadratic volume boundaries are unsupported; no silent triangulation/fallback occurs.
  • API validation covers both orders, but the volume UI's second-order control remains disabled. Do not imply TET10 is currently enabled through that control.

Service handles virtual preview IDs, selected solver mappings and persistent insertion through the shared GMSH-backed mesh layer. Remesh/spline preview quality is deferred until accept. Deploy compatible Viewer, Service and Engine/PyAPI artifacts; the selector alone does not add capability to an old backend.

Phase6C checkpoints: Viewer ad2e3409, Service 1bb878a5, Engine 4f6cb36b. Editor build/typecheck passed; publication/deployment and full production numerical acceptance remain separate. See the Engine integration guide for runtime/deployment verification.

This package provides TypeScript declaration files for the Femsolve Cloud Services 3D Viewer/Editor.

Installation

To install the package, run the following command:

npm install fcs-core-viewer

Development Environment

There are different build configurations depending on what type of product derivative we want to build.

  1. Viewer3D Build Configurations This version's entry point is under the Viewer3D/Viewer3DAPI.ts file. The NPM command will build with webpack the fcs-viewer-3d.min.js bundle.

Debug build:

npm run build:vdev

Release build:

npm run build:vprod

Local hot-reload debug build:

npm run vserver
  1. Editor3D Debug Build The entry point is set at Editor3D/Editor3DAPI.ts and this compiles the completely fused source code of the Viewer3D and Editor3D.

Debug build:

npm run build:edev

Release build:

npm run build:eprod

Local hot-reload debug build:

npm run eserver