Add warning for @ prefix in build.transpile

MasterCarl commented 2 months ago

Describe the feature

Summary

Warn users about incorrect @scoped/package usage instead of scoped/package in build.transpile array.

Background

Following an upgrade from Nuxt 3.12.4 to 3.13.1, usage of the @hyperdx/lucene from another Nuxt layer suddenly threw an error:

The requested module '/_nuxt/@fs/.../monorepo/frontend/node_modules/@hyperdx/lucene/lib/lucene.js?v=7e5012eb' does not provide an export named 'toString'

This issue seems related to https://github.com/nuxt/nuxt/issues/28631

I was able to solve the problem by adding

build: {
    transpile: [
      "hyperdx/lucene",
    ],
  },

to my nuxt.config.ts. As pointed out in https://github.com/nuxt/nuxt/issues/24064#issuecomment-1788740269,

Note in the transpile array there is no @ before typeform/embed,

the @ scope prefix from the npm package name needed to be omitted.

It would be helpful to get a warning or error message about the (presumably) incorrect @ prefixing of packages to be transpired.

Alternatives and questions

Could the implementation be changed to work correctly with @scoped/packages?
Would this better be fixed in another package?

Additional information

[X] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

danielroe commented 2 months ago

This is a bug - you should be able to add '@hyperdx/lucene`. Would you be able to provide a reproduction? 🙏

github-actions[bot] commented 2 months ago

Would you be able to provide a reproduction? 🙏

More info

### Why do I need to provide a reproduction? Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making. ### What will happen? If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect. If `needs reproduction` labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it. ### How can I create a reproduction? We have a couple of templates for starting with a minimal reproduction: 👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz 👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox A public GitHub repository is also perfect. 👌 Please ensure that the reproduction is as **minimal** as possible. See more details [in our guide](https://nuxt.com/docs/community/reporting-bugs/#create-a-minimal-reproduction). You might also find these other articles interesting and/or helpful: - [The Importance of Reproductions](https://antfu.me/posts/why-reproductions-are-required) - [How to Generate a Minimal, Complete, and Verifiable Example](https://stackoverflow.com/help/minimal-reproducible-example)

github-actions[bot] commented 1 month ago

This issue was closed because it was open for 7 days without a reproduction.

nuxt / nuxt