-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[PRO]: Issue with deploying Pro Extensions on Render.com #4487
Comments
@prabir-vora How did you solve this problem ?? |
I seem to be facing the same issue. Has anyone else solved this? |
npm config set "@tiptap-pro:registry" https://registry.tiptap.dev/ npm install --save @tiptap-pro/extension-unique-id npm ERR! A complete log of this run can be found in: C:\Users\omara\AppData\Local\npm-cache_logs\2024-04-03T10_22_37_771Z-debug-0.log I am facing the same problem and I cannot solve it |
Hi @OmarAlkadri @martzoukos @ccreusat, here's how I got this to work with Docker deploy - You must copy your .npmrc into the Docker work directory before you run the
I hope this helps. |
Did you solve it? |
No, I've switched to Cloudflare Pages for my SPA and I build the bundle on my computer, so I don't face this issue now (but maybe once I set up CI/CD I'll need to come back to it :( ) |
I have no experience with Render.com and can only help out with actual issues of the npmrc file. If the npmrc credentials are not passed around correctly on Render.com's side we can't really do a lot to help. |
When I execute npm install on my dev env, it will also report 403 |
Did you setup your .npmrc correctly and is your npm installation using it?
or do # tiptap
npm config get @tiptap-pro:registry # hocuspocus
npm config get @hocuspocus-pro:registry if you have everything setup and |
https://cloud.tiptap.dev/pro-extensions <--- please complete that steps |
Which packages did you experience the bug in?
extension-mathematics, extension-emoji, etc.
What Tiptap version are you using?
Latest
What’s the bug you are facing?
I am deploying my backend service on Render.com using a Docker container. I have the TipTap pro auth token in my .npmrc file.
Here is the build logs indicating the error:
-------START-----
Sep 28 11:23:25 PM #10 [base 4/8] RUN npm install --legacy-peer-deps && npm run postinstall
Sep 28 11:24:09 PM #10 43.61 npm notice
Sep 28 11:24:09 PM #10 43.61 npm notice New major version of npm available! 8.19.2 -> 10.1.0
Sep 28 11:24:09 PM #10 43.61 npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.1.0
Sep 28 11:24:09 PM #10 43.61 npm notice Run
npm install -g npm@10.1.0
to update!Sep 28 11:24:09 PM #10 43.61 npm notice
Sep 28 11:24:09 PM #10 43.61 npm ERR! code E404
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@tiptap-pro%2fextension-mathematics - Not found
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404 '@tiptap-pro/extension-mathematics@^2.2.4' is not in this registry.
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404 Note that you can also install from a
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404 tarball, folder, http url, or git url.
Sep 28 11:24:09 PM #10 43.62
Sep 28 11:24:09 PM #10 43.62 npm ERR! A complete log of this run can be found in:
Sep 28 11:24:09 PM #10 43.62 npm ERR! /root/.npm/_logs/2023-09-29T06_23_26_104Z-debug-0.log
Sep 28 11:24:09 PM #10 ERROR: process "/bin/sh -c npm install --legacy-peer-deps && npm run postinstall" did not complete successfully: exit code: 1
Sep 28 11:24:09 PM ------
Sep 28 11:24:09 PM > [base 4/8] RUN npm install --legacy-peer-deps && npm run postinstall:
Sep 28 11:24:09 PM #10 43.61 npm ERR! code E404
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@tiptap-pro%2fextension-mathematics - Not found
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404 '@tiptap-pro/extension-mathematics@^2.2.4' is not in this registry.
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404 Note that you can also install from a
Sep 28 11:24:09 PM #10 43.62 npm ERR! 404 tarball, folder, http url, or git url.
Sep 28 11:24:09 PM #10 43.62
Sep 28 11:24:09 PM #10 43.62 npm ERR! A complete log of this run can be found in:
Sep 28 11:24:09 PM #10 43.62 npm ERR! /root/.npm/_logs/2023-09-29T06_23_26_104Z-debug-0.log
Sep 28 11:24:09 PM ------
Sep 28 11:24:09 PM Dockerfile:7
Sep 28 11:24:09 PM --------------------
Sep 28 11:24:09 PM 5 | COPY package.json ./
Sep 28 11:24:09 PM 6 |
Sep 28 11:24:09 PM 7 | >>> RUN npm install --legacy-peer-deps && npm run postinstall
Sep 28 11:24:09 PM 8 |
Sep 28 11:24:09 PM 9 | COPY prisma/schema.prisma ./prisma/
Sep 28 11:24:09 PM --------------------
Sep 28 11:24:09 PM error: failed to solve: process "/bin/sh -c npm install --legacy-peer-deps && npm run postinstall" did not complete successfully: exit code: 1
Sep 28 11:24:09 PM error: exit status 1
------END------
I am using pro extensions on both my React front-end (deployed on Vercel) and Nest.js Backend Service (deployed on Render.com). The front end deploys perfectly. However, on the backend, the build fails with unable to fetch npm packages from the private registry for all pro extensions.
Here is what my .npmrc looks like:
@tiptap-pro:registry=https://registry.tiptap.dev/
//registry.tiptap.dev/:_authToken=MY_AUTH_TOKEN
What browser are you using?
Chrome
Code example
No response
What did you expect to happen?
The build should work perfectly.
Anything to add? (optional)
No response
Did you update your dependencies?
Are you sponsoring us?
The text was updated successfully, but these errors were encountered: