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

Fresh lume site fails: "could not find npm package markdown-it-attrs" #340

Closed
Sam-Spencer opened this issue Dec 21, 2022 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@Sam-Spencer
Copy link

Version

1.14.2

Platform

macOS

What steps will reproduce the bug?

  1. Install the latest stable version of node (18.12.1)
  2. Create an empty directory
  3. Follow the instructions to get started with Luke exactly as they are provided in the docs
  4. Use a typescript config
  5. Do not add any plugins
  6. Create your first page: index.md (again, as stated in the docs)
  7. Run deno task serve (as per the docs)
  8. The following error prints in the terminal:

error: Could not find npm package 'markdown-it-attrs' matching 4.1.6. Try retrieving the latest npm package information by running with --reload

How often does it reproduce? Is there a required condition?

Every time

What is the expected behavior?

Should be able to initialize a new lime site by following the provided instructions

What do you see instead?

There is an ambiguous npm package error:

error: Could not find npm package 'markdown-it-attrs' matching 4.1.6. Try retrieving the latest npm package information by running with --reload

Interestingly, that specific version of that specific npm package does exist and was published 10 days ago (at time of writing).

Additional information

No response

@Sam-Spencer Sam-Spencer added the bug Something isn't working label Dec 21, 2022
@oscarotero
Copy link
Member

oscarotero commented Dec 21, 2022

Hi, @Sam-Spencer
This is a bug from Deno, related with how they cache the NPM packages. (See denoland/deno#16901)

There are two possible solutions:

  • Purge the Deno's cache folder (run deno info to get the cache path)
  • Or run echo "import 'lume/cli.ts'" | deno run --unstable -A --reload - (The same command of deno task lume but with the --reload flag). This will refresh the Deno's cache.

@officialrajdeepsingh
Copy link
Contributor

officialrajdeepsingh commented Dec 27, 2022

The following echo "import 'lume/cli.ts'" | deno run --unstable -A --reload - command does not work for me, then I run the following command, it will be fine for me.

 deno cache --reload ./_config.ts 

@oscarotero
Copy link
Member

This was fixed in Deno. So I'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants