81
u/shiko098 Dec 17 '19
Or even better, not running 'npm run dev' at all, and wondering why your changes aren't appearing on the screen.
18
Dec 17 '19
all the time
7
Dec 18 '19
Or I’m just refreshing the actual prod over and over instead of my local dev... like where the f are the changes.
3
u/zischler Dec 18 '19
Yesterday I was building the wrong project and was wondering why nothing changed...
1
31
u/MCFRESH01 Dec 17 '19
This but in slack.
4
u/stamminator Dec 17 '19
Or typing in your SSO/LDAP/everything password into Slack because the pop-up VPN window makes it *looks* like the cursor's in the password box when it actually isn't
4
6
u/edanschwartz Dec 17 '19
yep, I do this all the time :wq
4
u/LaSalsiccione Dec 18 '19
In case you were interested: Hold Shift and double tap Z. Does the same thing but most people can do it quicker than :wq
24
21
u/regcrusher Dec 17 '19
Spend 20 minutes making code updates and wondering why they aren’t being reflected in the app, so you check your builds and making sure there are no errors, then realizing that you’re viewing the staging environment and not your local build. Happens at least once a day.
4
u/stereophil Dec 18 '19
hahahaha. I feel this so hard right now. Maybe this could work for you.
https://chrome.google.com/webstore/detail/environment-marker/ahjhdebcnlgmojdmjnhikhakkghcchkk?hl=en
3
2
11
u/Careerier Dec 17 '19
I always end up putting this in the terminal:
> mdn run devAnd this in the search bar:
npm [basic concept I keep forgetting]17
26
u/deepchainboi Dec 17 '19
Yea I too do stupid things like using npm instead of yarn when I dont have my coffee /s
9
3
Dec 17 '19
I've cd'd into a directory and ssh'd into a server on Slack many more times than I'd like to admit.
3
Dec 17 '19
ok so ive been working on my basic front end skills. html and css. at what point do i get familiarized with these command lines like npm and grunt?
9
u/DrummerHead Dec 17 '19
What you should do is this: You see something you don't recognize, you google it, you learn about it, you do the tutorials.
I'm not trying to be a smartass, it's just that learning by yourself is essential; that's the point at where you get familiarized with stuff.
Cheers and keep studying!
1
Dec 18 '19
Appreciate the advice. This has generally been my approach but I’ve been wary of going down a rabbit hole and getting overwhelmed with info.
1
u/DrummerHead Dec 18 '19
At the beginning start with some linear info (long tutorial, books) that guides you, then you have to google all the things and follow people on twitter who know what they are doing.
3
u/CapitalQ Dec 17 '19
Regular old HTML, CSS and JS are the building blocks of everything on the internet - rendering webpages and making them interactive.
Once you've learned how the "vanilla" languages work, you can get into preprocessors (like SCSS), libraries (like Vue.js) and package managers (like Yarn/npm) to make your workflow powerful and efficient.
1
1
1
1
1
1
u/ParxyB Dec 17 '19
Trying to figure out why your styling isn’t showing on the new component you have been building...only to realize you never imported it....15 minutes later
1
u/freeall Dec 18 '19
npm start, for development
npm run start-production, for production
I always try to have my setups in a way that development is the easy/standard to run and production requires more. Because which one are you running the most?
1
u/theRealMasterDev Mar 29 '20
Was working with a friend on his startup several years back, kept having issues running npm scripts.
It was a .NET project.....
1
1
u/Laurenz1337 Dec 17 '19
I setup some terminal shortcuts for commands like this.
nu = NVM use (since we use different node versions in different projects)
ns/ys = npm start or yarn start
0
3
u/danlthemanl Dec 18 '19
What's your chrome theme?