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

Publish nightly builds #562

Closed
tobiasdiez opened this issue Apr 23, 2024 · 11 comments · Fixed by #748
Closed

Publish nightly builds #562

tobiasdiez opened this issue Apr 23, 2024 · 11 comments · Fixed by #748
Assignees
Labels
type: chore Helpful for the development of this module

Comments

@tobiasdiez
Copy link
Collaborator

Todo: configure secret NPMJS_TOKEN with the correct deployment token.

@tobiasdiez tobiasdiez added the type: chore Helpful for the development of this module label Apr 25, 2024
@hp-vev
Copy link

hp-vev commented May 1, 2024

Not sure if this is related but I am having some issues withTypeError when reading '__STORYBOOK__' property of undefined. I noticed there is already a fix for that, but it hasn't been released if I am correct?

@blowsie
Copy link
Contributor

blowsie commented May 29, 2024

Not sure if this is related but I am having some issues withTypeError when reading '__STORYBOOK__' property of undefined. I noticed there is already a fix for that, but it hasn't been released if I am correct?

I too have this issue

using windows with the below empty project

pnpm dlx nuxi@latest init myproject
cd myproject
pnpm dlx nuxi@latest module add storybook
pnpm dlx storybook-nuxt init
 ERROR  (node:41760) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.                                                                                                                                                                                                                                                  14:12:49  
(Use node --trace-deprecation ... to show where the warning was created)


 ERROR  Cannot start nuxt:  Cannot read properties of undefined (reading '__STORYBOOK__') 

Nuxt 3.11.2 with Nitro 2.9.6

@kasperpeulen
Copy link

I can recommend https://github.com/intuit/auto to automate the release process.

@blowsie
Copy link
Contributor

blowsie commented Jun 3, 2024

The examples are also broken
https://storybook.nuxtjs.org/examples/basic

@tobiasdiez
Copy link
Collaborator Author

@chakAs3 could you please add the required secrets? Thanks a lot! 🚀

@shilman
Copy link

shilman commented Jun 4, 2024

Thanks @tobiasdiez @chakAs3 for being on top of this. 🙏

@mehcode
Copy link
Contributor

mehcode commented Jun 14, 2024

@chakAs3 @tobiasdiez Can we please set this up? I would personally be a lot more motivated to contribute if I could use those contributions quickly without waiting for a formal release.

@chakAs3
Copy link
Collaborator

chakAs3 commented Jul 30, 2024

@tobiasdiez @mehcode sorry guys,i just payed attention to this notification, it is already done i updated the token

@tobiasdiez
Copy link
Collaborator Author

@chakAs3 Thanks a lot! However, it currently fails with

npm notice Publishing to https://registry.npmjs.org/ with tag nightly and public access
npm error code EOTP
npm error This operation requires a one-time password from your authenticator.
npm error You can provide a one-time password by passing --otp=<code> to the command you ran.
npm error If you already provided a one-time password then it is likely that you either typoed
npm error it, or it timed out. Please try again.

Could you please make sure that you use the "automation" kind of token:

@chakAs3
Copy link
Collaborator

chakAs3 commented Aug 9, 2024

it is done 👍 @tobiasdiez

@tobiasdiez
Copy link
Collaborator Author

Awesome! This is working now. 🚀

tobiasdiez added a commit that referenced this issue Aug 11, 2024
<!--
☝️ PR title should follow conventional commits
(https://conventionalcommits.org).
In particular, the title should start with one of the following types:

- docs: 📖 Documentation (updates to the documentation or readme)
- fix: 🐞 Bug fix (a non-breaking change that fixes an issue)
- feat: ✨ New feature/enhancement (a non-breaking change that adds
functionality or improves existing one)
- feat!/fix!: ⚠️ Breaking change (fix or feature that would cause
existing functionality to change)
- chore: 🧹 Chore (updates to the build process or auxiliary tools and
libraries)
-->

### 🔗 Linked issue

<!-- If it resolves an open issue, please link the issue here. For
example "Resolves #123" -->

### 📚 Description

Final step to fix #562

<!-- Describe your changes in detail -->
<!-- Why is this change required? What problem does it solve? -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: chore Helpful for the development of this module
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants