I update an old repo: https://github.com/cbartel/nw-company-tool The creator of this project created a tutorial which explains how to install everything, only if you use his node distribution.
My question is: how do I recreate the same node distribution using the files in the tar.gz release?
What are the steps? Installing nest? then what? should I install angular? or? Should I run the build.ts? I don't know from where should I start. I come from Python. I know basic html, but I don't know how prisma, angular, nest, node and everything work.. I read and watch tutorials about the basic, but I still don't know where should I start for making that GitHub work on my Ubuntu server without using the guy's node distribution.
Can someone be so kind to check his repo and tell me from where to start? Will be really appreciate. I spent 40+ hours trying to start all .ts file but only with errors and unsuccessfully.
I tried to run in terminal the commands the ts script use, but got the same errors.
what am I missing?
I tried every command I found on the internet to fix the errors, but created just more errors.
I'm using Digital Ocean Ubuntu 20 as server with domain buy from ionos.
I try to run line of commands present in the files build.ts and other ts files. nothing works.
If I use his node distribution I get 0 errors. but the files are changed, and for doing 1 update, or add some data, I need to change 12 js files or more, that's why I'm trying to setup my distribution so I can edit just 4 files and everything should work fine, but I don't know how to create the same node distribution the guy released on his GitHub. I'm using his same files and I don't understand what is wrong.
Related
I began a Reactjs tutorial project using Sanity for backend stuff. For 3 days now I am unable to do anything at all. The only thing that works (at random) is sanity start to open my backend schemas in the browser I get a million errors wwhen I try to install packages, open my Reactjs app in the browser, or even move files into my vs code. I have uninstalled VS Code and Node a dozen times now. Please, please, please can anybody help me.
All suggestions will be greatly appreciated as I am a complete noob in the web dev space.
I tried uninstalling and reinstalling nodejs, my code editor (i.e VS Code), have restarted the project from scratch and tried to load other, smaller and simpler beginner Reactjs builds I did before, and even they do not open.
The most recent error is the localhost refusing to open. Along with being unable to install react-icons and node-sass, amongst others.
this is my first question ever. I'm trying to run an Adonis.js app by entering adonis serve --dev at the terminal. The messages are always the same in this succession:
SERVER STARTED
Watching files for changes...
Fatal error in , line 0
Check failed: U_SUCCESS(status).
FailureMessage Object: 000000D7655ECBA0Application crashed, make sure to kill all related running process, fix the issue and re-run the app
The only thing that changes is the FailureMessageObject. My Node version is 12.0, npm 6.9.
I can't say anything seriously working on your situation cause you gave me no detailed data but I know that surely you are doing something wrong.
It could be better if you at least mentioned the version of adonisjs you've been using.
Anyway, if you learned to run your server from a video from someone else's youtube channel, I strongly recommend you to read documentation and stop watching those videos.
And for adonisjs there are 2 different documentation:
adonisjs's Documentation, version 4.1 or less.
You can change the version on top left combo box.
adonisjs's preview Documentation, version 5.0.
Actually the documentation is not still completed at this time but the version is stable. yeah, that's the reason why I wrote preview.
And that's it, start recreating an adonisjs app from documentation guides.
I solved it. It was something with node or npm. I followed this steps enumerated in this post: How to completely remove node.js from Windows. Reinstalled node. Installed Adonis and it's CLI again and created an app and this time the app didn't crashed, and ran smoothly (after that I also created some migrations and they too worked well).
Having a bit of an issue with Heroku. I've always uploaded in one directory, but this time I wanted my folder structure to be a bit more, well structured. The problem is I can't seem to upload to Heroku like this.
I have a directory containing a folder called "client" which contains my angular 9 application and I have a folder called "middle-tier" containing the node.js server application.
I can't figure out how to push this up and allow it to work. The node application serves the angular application.
Everything works locally I just have no idea how to push this up to Heroku servers.
Please see attached screenshots of the structure.
Below is the error message I'm getting. Which I tried to fix by running git init again in the root of the structure. And then running the command to have a node.js build pack. Which was to no avail this also did not work and produced the same problem.
I have tried to include as much detail as I can but if there is anything else I can provide please let me know. I've spent quite some time building my application and am quite eager to deploy it!
Thanks for your time guys!
In short, with multiple discussions with Heroku support line, at the moment it is impossible to upload a mono repo to a single Heroku instance.
I want to create a proxy-server in Node.js and I'm trying to figure out what npm-package to use. I recently read some people are trying to create malware packages with similar names to frequently used npm-packages (typosquatting, source). That made me suspicious when I saw the name 'httpp-proxy' just before installing.
Does anyone know the difference between the http-proxy and httpp-proxy packages?
I looked into http-proxy and it looked like it had a big community
262,764 downloads in the last day
1,604,883 downloads in the last week
6,922,320 downloads in the last month
You can safely use that
I started "using" Grunt.js yesterday, it seems to nest extensively deep folder structures in my projects, that look something like this:
assets\bootstrap\node_modules\grunt-contrib-jshint\node_modules\jshint\node_modules\cli\node_modules\glob\node_modules\minimatch\node_modules\brace-expansion\node_modules\balanced-match\Makefile
This still is a realtively short path, but there are loads of paths generated which my PC (running Windows 7) simply can't handle. I see this a well known issue as you can read in this Github issue of Node.js from 2014:
https://github.com/nodejs/node-v0.x-archive/issues/6960#issuecomment-46704998
However the issue still isn't fixed and a lot of people seem to be mad about it.
I wonder if I should get my head around Grunt at all because I didn't see a solid solution to get this working for me so far.
Even if I started using Mac (assumed Grunt.js works fine on mac), from my point of view Grunt seems to be a bad option if you want to be able to collaborate with people using windows.
Is there an easy way to use Gruntjs without running into file path issues on Windows?
*update: This is what GIT BASH throws at me when I am trying to track my files using git add .
warning: unable to access 'node_modules/grunt-contrib-compass/node_modules/bin-v ersion-check/node_modules/bin-version/node_modules/find-versions/node_modules/me ow/node_modules/read-pkg-up/node_modules/find-up/node_modules/pinkie-promise/nod e_modules/pinkie/.gitignore': Filename too long
Solution is to use GULP Or move your project to root directory of your drive, I am not sure if this is a grunt specific issue or rather a node specific issue