@ferlab/next
Advanced tools
npm run dev to test the build with your changesnpm link here in ferlab-nextnpm link @ferlab/next in your local wrapper-next project to connect ferlab-next and import it.But currently the start doesn't work because there are incompatibility with duplicate graphql module when we start the wrapper-next with ferlab-next in link.
So use pack feature:
npm run pack here in ferlab-next: it builds and creates the file "ferlab-next-x.x.x.tgz"npm install ../ferlab-next/ferlab-next-x.x.x.tgz in your local wrapper-next projectnpm run testStarter helped by https://advancedweb.hu/modern-javascript-library-starter
FAQs
Shared library for our wrappers GraphQL APIs
We found that @ferlab/next demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.