Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unclear how hugo mod npm pack works #1980

Open
willfaught opened this issue Feb 21, 2023 · 0 comments
Open

Unclear how hugo mod npm pack works #1980

willfaught opened this issue Feb 21, 2023 · 0 comments

Comments

@willfaught
Copy link
Contributor

willfaught commented Feb 21, 2023

Prepares and writes a composite package.json file for your project.
On first run it creates a "package.hugo.json" in the project root if not already there. This file will be used as a template file
with the base dependency set.
This set will be merged with all "package.hugo.json" files found in the dependency tree, picking the version closest to the project.
This command is marked as 'Experimental'. We think it's a great idea, so it's not likely to be
removed from Hugo, but we need to test this out in "real life" to get a feel of it,
so this may/will change in future versions of Hugo.

It's unclear from this:

  • That it creates project.json (PJ) if it doesn't exist
  • What's in PJ or package.hugo.json (PHJ) if they're created
    • Also why is comments there? Why is an empty devDeps there?
  • What's in PHJ if it's created and PJ exists
  • What's in PJ if it's created and PHJ exists
  • What happens if PJ and PHJ exist and don't match
  • What happens to PJ if PHJ is updated, or vice versa
  • If you should check in PHJ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant