Skip to content

About

ferlab-next

Resources

Stars

0 stars

Watchers

4 watching

Forks

Repository files navigation

ferlab repository img

ferlab-next

Development

  • Execute: npm run dev to test the build with your changes

dev and connect with local wrapper-next project (without live reload):

with yalc

  • install yalc if not already: npm install -g yalc
  • Execute (every change): yalc publish here in ferlab-next
  • Execute (every change): yalc add @ferlab/next in your local cqdg-wrapper-api

with npm link (but not working with duplicate graphql module)

  • Execute: npm link here in ferlab-next
  • Execute: npm 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:

  • Execute: npm run pack here in ferlab-next: it builds and creates the file "ferlab-next-x.x.x.tgz"
  • Execute npm install ../ferlab-next/ferlab-next-x.x.x.tgz in your local wrapper-next project
  • Then you are allow to run dev your local wrapper-next project with the pack without have to push to npm your local of ferlab-next

Test

  • Execute: npm run test

Push to npm

  • Update version in package.json
  • push on main automatically publish to npm

About

ferlab-next

Resources

Stars

0 stars

Watchers

4 watching

Forks

Releases

Packages

Used by

Contributors

Languages