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.

Sign up for GitHub

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

Jump to bottom

Missing "./playground/.nuxt/css" export in "my-module" package #22

Closed
MohammadS3dd opened this issue Jan 31, 2022 · 9 comments
Closed

Missing "./playground/.nuxt/css" export in "my-module" package #22

MohammadS3dd opened this issue Jan 31, 2022 · 9 comments
Assignees
@danielroe

Comments

@MohammadS3dd
Copy link

i'm following guides for making a new module and this weird error keeps popping up.
image
@MohammadS3dd
Copy link
Author

i fidgeted with this and turns out this only occurs in windows. doesn't matter if i run the project with yarn, npm or pnpm... but everything works fine with wsl on the same project.

@lihbr
Copy link
Member

lihbr commented Feb 7, 2022 •
edited
Loading

Experiencing the same one here, still troubleshooting a temp fix here~

I'm running Node v16.13.0 and I was able to reproduce using the starter.

@danielroe danielroe self-assigned this Feb 7, 2022
@danielroe
Copy link
Member

danielroe commented Feb 7, 2022 •
edited
Loading

A temporary workaround is to name the exports section of your package.json to _exports (i.e. disable it but without removing it from the file, so you can re-activate once this is resolved).

For now, just create a minimal package.json file in your playground/ directory.

This was referenced Feb 7, 2022
Merged
Closed
@Intevel
Copy link

Intevel commented Mar 3, 2022

nuxt/nuxt#13403

@ricardogobbosouza
Copy link
Contributor

i think this has been resolved

@Intevel
Copy link

Intevel commented Mar 11, 2022

Yes, thank you @danielroe ❤️

@danielroe
Copy link
Member

Do you mean this is no longer replicable, or that it is resolved with my workaround?

@Intevel
Copy link

Intevel commented Mar 11, 2022

It's solved with a package.json for me. @danielroe

@danielroe danielroe mentioned this issue Mar 18, 2022
Closed
@pi0 pi0 mentioned this issue Apr 4, 2022
Closed
@Intevel
Copy link

Intevel commented Apr 4, 2022

I think this can be closed. Or maybe we can fix this bug in general by creating a package.json?
So that when I create a new module already in the playground is automatically created a package.json.

@pi0 pi0 closed this as completed Apr 4, 2022
danielroe added a commit to nuxt-modules/google-fonts that referenced this issue Jul 20, 2022
@danielroe
test: add package.json stubs for windows
ed9a051 
nuxt/module-builder#22
ricardogobbosouza added a commit to nuxt-modules/google-fonts that referenced this issue Jul 22, 2022
@ricardogobbosouza @danielroe
feat!: add support for nuxt 3/nuxt bridge (#94)
fbe5d77 
* refactor: use @nuxt/kit

* feat: support `vue-meta` and `@vueuse/head`

* feat: use nitro publicAssets

* chore: update lock files

* fix: add semicolon

* chore: use yarn

* chore: add playground

* fix: parse fonts on head

* test: update using `@nuxt/test-utils`

* test: don't rely on nuxt context to get rootDir

* chore: run vitest only once

* chore: upgrade nuxt to rc6

* test: add package.json stubs for windows

nuxt/module-builder#22

* test:  simplify

Co-authored-by: Daniel Roe <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@danielroe danielroe

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@pi0 @ricardogobbosouza @lihbr @danielroe @MohammadS3dd @Intevel