[{"data":1,"prerenderedAt":359},["ShallowReactive",2],{"article-npm-dependencies-vs-devdependencies":3},{"article":4,"tags":120,"previous":148,"next":294},{"id":5,"title":6,"author":7,"body":8,"createdAt":107,"description":108,"extension":109,"img":110,"meta":111,"navigation":112,"path":113,"seo":114,"stem":115,"tags":116,"updatedAt":107,"__hash__":119},"articles\u002Farticles\u002Fnpm-dependencies-vs-devdependencies.md","NPM - dependencies vs devDependencies",null,{"type":9,"value":10,"toc":103},"minimark",[11,15,18,28,31,57,66,93],[12,13,14],"p",{},"Technically, when using a bundler like webpack, the result will not make a difference with regard to the output of your bundling process.",[12,16,17],{},"That being said, dividing the packages in dependencies and devDependencies still helps you (and others looking at your package.json) to understand which packages are meant to end up being a part of the bundle created (dependencies), and which are needed to build the bundle only (devDependencies).",[12,19,20,21,24,25,27],{},"Just remember main principle:",[22,23],"br",{},"\n-> If you need package in production put it into dependencies (most likely axios should be in dependencies in your case).",[22,26],{},"\n-> If you need package only during development, put it into devDependencies (e.g. unit-test libraries, which isn't needed in productions should be in devDependencies",[12,29,30],{},"Summary of important behavior differences:",[12,32,33,41,42,44,47,48,51,53,56],{},[34,35,37],"a",{"href":36},"https:\u002F\u002Fgithub.com\u002Fnpm\u002Fnpm\u002Fblob\u002F2e3776bf5676bc24fec6239a3420f377fe98acde\u002Fdoc\u002Ffiles\u002Fpackage.json.md#dependencies",[38,39,40],"code",{},"dependencies"," are installed on both:",[22,43],{},[38,45,46],{},"npm install"," from a directory that contains ",[38,49,50],{},"package.json",[22,52],{},[38,54,55],{},"npm install $package"," on any other directory",[12,58,59,65],{},[34,60,62],{"href":61},"https:\u002F\u002Fgithub.com\u002Fnpm\u002Fnpm\u002Fblob\u002F2e3776bf5676bc24fec6239a3420f377fe98acde\u002Fdoc\u002Ffiles\u002Fpackage.json.md#devdependencies",[38,63,64],{},"devDependencies"," are:",[12,67,68,69,71,72,74,75,78,79,81,82,85,86,89,90,92],{},"also installed on ",[38,70,46],{}," on a directory that contains ",[38,73,50],{},", unless you pass the ",[38,76,77],{},"--production"," flag.",[22,80],{},"\nnot installed on ",[38,83,84],{},"npm install \"$package\""," on any other directory, unless you give it the ",[38,87,88],{},"--dev"," option.",[22,91],{},"\nare not installed transitively.",[12,94,95,96],{},"Reference: ",[34,97,102],{"href":98,"target":99,"rel":100},"https:\u002F\u002Fstackoverflow.com\u002Fquestions\u002F18875674\u002Fwhats-the-difference-between-dependencies-devdependencies-and-peerdependencies\u002F22004559#22004559","_blank",[101],"noopener","StackOverflow",{"title":104,"searchDepth":105,"depth":105,"links":106},"",2,[],"2020-01-07T14:02:12.046Z","Webpack is one of those technologies that has become increasingly important and yet struggles to be clear and obvious for most developers.  One of the best ways to get up to speed is to start from scratch (empty package.json) and build up one piece at a time to understand how it works.  Below are some notes about package.json and how dependencies are established.","md","\u002Farticles\u002Fimages\u002Fnpm.png",{},true,"\u002Farticles\u002Fnpm-dependencies-vs-devdependencies",{"title":6,"description":108},"articles\u002Fnpm-dependencies-vs-devdependencies",[117,118],"vuejs","npm","6JDIyAP2t28x6-aZhXKViT2l9gCy3dbGWKBsP3m-43Y",[121,135],{"id":122,"title":123,"body":124,"description":128,"extension":109,"img":129,"meta":130,"name":118,"navigation":112,"path":131,"seo":132,"stem":133,"__hash__":134},"tags\u002Ftags\u002Fnpm.md","Npm",{"type":9,"value":125,"toc":126},[],{"title":104,"searchDepth":105,"depth":105,"links":127},[],"npm is two things... first and foremost, it is an online repository for the publishing of open-source Node.js projects; second, it is a command-line utility for interacting with said repository that aids in package installation, version management, and dependency management.","https:\u002F\u002Fimages.unsplash.com\u002Fphoto-1598313183973-4effcded8d5e?ixlib=rb-1.2.1&ixid=eyJhcHBfaWQiOjEyMDd9&auto=format&fit=crop&w=675&q=80",{},"\u002Ftags\u002Fnpm",{"description":128},"tags\u002Fnpm","lIC-Oaulb8LKEOVAMw2ea29_Ir9k8IMaGOx8do5mHaI",{"id":136,"title":137,"body":138,"description":142,"extension":109,"img":129,"meta":143,"name":117,"navigation":112,"path":144,"seo":145,"stem":146,"__hash__":147},"tags\u002Ftags\u002Fvuejs.md","Vuejs",{"type":9,"value":139,"toc":140},[],{"title":104,"searchDepth":105,"depth":105,"links":141},[],"Vue (pronounced \u002Fvjuː\u002F, like view) is a progressive framework for building user interfaces. Unlike other monolithic frameworks, Vue is designed from the ground up to be incrementally adoptable",{},"\u002Ftags\u002Fvuejs",{"description":142},"tags\u002Fvuejs","FLzo8HD9QLE9FzBr4K8hRvB7QUPBQ4Ku-dpXQK90QZM",{"id":149,"title":150,"author":7,"body":151,"createdAt":282,"description":283,"extension":109,"img":7,"meta":284,"navigation":112,"path":285,"seo":286,"stem":287,"tags":288,"updatedAt":282,"__hash__":293},"articles\u002Farticles\u002Fsource-control-options-git-and-team-foundation-server-tfs.md","Source Control Options GIT and Team Foundation Server (TFS)",{"type":9,"value":152,"toc":277},[153,158,175,178,201,204,211,221,236,240,247,250,259,266,269],[154,155,157],"h3",{"id":156},"git-is-a-distributed-version-control-system","Git is a Distributed Version Control System",[159,160,161,169],"ul",{},[162,163,164,168],"li",{},[165,166,167],"strong",{},"Each developer"," has the entire repository, including the entire change history on his\u002Fher local machine",[162,170,171,174],{},[165,172,173],{},"The developer"," can see changeset history offline or commit (check-in) changes offline to his local repository",[12,176,177],{},"Since the entire repository is local, we do everything locally. This includes, but not limited to:",[159,179,180,183,186,189,192,195,198],{},[162,181,182],{},"Committing changes (Check-in)",[162,184,185],{},"Viewing commit history",[162,187,188],{},"Creating a new branch",[162,190,191],{},"Merging branches",[162,193,194],{},"Moving to a different branch",[162,196,197],{},"Deleting branches",[162,199,200],{},"Reverting older commits",[12,202,203],{},"Yes we do have to Check-in or 'Push' our changes to the remote repository.",[12,205,206,207,210],{},"'Check-in' within Git is divided into ",[165,208,209],{},"2 parts",":",[12,212,213,216,217,220],{},[165,214,215],{},"Commit"," and **Push\n",[165,218,219],{},"Developers can now commit locally","whatever they want – Ugly code, comments, and work in progress. The other developers won’t get those changes as the commit is performed entirely local on their respective PC. When the code is ready for the team, they can Push the code changes to the remote repository.  This workflow gives the developer addition management of changes and when\u002Fhow things are pushed into the central repository for team consumption.",[12,222,223,224,227,228,231,232,235],{},"The ",[165,225,226],{},"Staging","concept …. this is like ",[165,229,230],{},"Included","\u002F",[165,233,234],{},"Excluded","changes in TFS. Only staged files will be committed. Again, why? (well say locally modified configuration files can stay out of source control)",[154,237,239],{"id":238},"branches-and-merges","Branches and Merges",[12,241,242,243,246],{},"In TFS\u002FTFSVC, ",[165,244,245],{},"Branch","will create a new directory with a copy of all files and directories of the parent Branch. For a developer to work on that new branch, they will have to copy that directory to his hard disk, essentially having another folder with the source code.",[12,248,249],{},"With Git, each branch is not a copy of the files from the parent branch. Instead, it’s simply a pointer to the Commit in the parent Branch from where we created our new branch.  With Git when working on a different branch, we tell Git “Move to another branch” (Checkout command) and Git will change our working area to match the desired branch. Again, there is a performance benefit as this entire action is performed locally.  Git already contains all the branches on the local machine.",[12,251,252,255,256,258],{},[165,253,254],{},"Merging"," is a lightweight operation. We can merge any branch to any branch. We can merge the entire difference or a specific Commit. Git will find the “Base” Commit where the branches split and allow us to resolve conflicts (This is the same as in TFS)",[22,257],{},"\nA good practice with Git is to create a new branch to work on a big feature. Eventually, merging that branch to the master branch and discarding the new branch entirely.",[12,260,261],{},[34,262,265],{"href":263,"target":99,"rel":264},"https:\u002F\u002Fgit-scm.com\u002Fbook\u002Fen\u002Fv2\u002FGit-Branching-Branches-in-a-Nutshell",[101],"Reference\u002FTutorial on GIT branching",[12,267,268],{},"TFS\u002FTFVC is Centralized Version Control System",[159,270,271,274],{},[162,272,273],{},"the developer has a copy of the repository file system on his machine",[162,275,276],{},"offline actions like commits (check-ins)  and seeing history are impossible since the local repository can’t save “changes”",{"title":104,"searchDepth":105,"depth":105,"links":278},[279,281],{"id":156,"depth":280,"text":157},3,{"id":238,"depth":280,"text":239},"2020-01-21","Git has been gaining momentum lately and continues to be the path forward for all organizations (including Microsoft) as the source control of record.  What are the differences, benefits...read more...",{},"\u002Farticles\u002Fsource-control-options-git-and-team-foundation-server-tfs",{"title":150,"description":283},"articles\u002Fsource-control-options-git-and-team-foundation-server-tfs",[289,290,291,292],"sourcecontrol","teamfoundationserver","visualstudio","git","z27ZBLeINXv4DaOx5aV-Ihtuz5pCxHT3joVG2EXl5Z0",{"id":295,"title":296,"author":7,"body":297,"createdAt":350,"description":351,"extension":109,"img":7,"meta":352,"navigation":112,"path":353,"seo":354,"stem":355,"tags":356,"updatedAt":350,"__hash__":358},"articles\u002Farticles\u002Fdatetimeoffset-confusion.md","DateTimeOffset Confusion",{"type":9,"value":298,"toc":348},[299,312,319,322,328,331,345],[12,300,301,302,305,306,308,309,311],{},"Consider the following timestamp: ",[165,303,304],{},"1995-07-14T13:05:00.0000000-03:00",".",[22,307],{},"\nWhen asked what the -03:00 at the end is called, many developers answer, “a time zone.”",[22,310],{},"\nWell…",[12,313,314,315,318],{},"The -03:00 does represent the offset from UTC.\nTo get the UTC time, ",[165,316,317],{},"invert"," the offset sign then add it to the time such as 13:05 + 3 = 16:05 in UTC.",[12,320,321],{},"Okay, following this ok now more details..",[12,323,223,324,327],{},[165,325,326],{},"mistake ","is in thinking that the offset is all there is to a time zone. Nope.",[12,329,330],{},"A time zone is a geographical area, and it consists of many pieces of information, such as",[159,332,333,336,339,342],{},[162,334,335],{},"One or more offsets. (DST is a thing, after all.)",[162,337,338],{},"The dates when DST transitions happen. (These can and do change whenever governments feel like it.)",[162,340,341],{},"The amount of time applied when transitions happened. (It’s not one hour everywhere.)",[162,343,344],{},"The historical records of changes to the above rules.",[12,346,347],{},"In short, is is not possible to establish the time zone by the offset!",{"title":104,"searchDepth":105,"depth":105,"links":349},[],"2019-12-11T14:02:13.400Z","For many years, dates, times, time zones, new language date types such as datetimeoffset have confused developers.  I am writing this in hopes that you can refresh some details about the often used datetimeoffset type.",{},"\u002Farticles\u002Fdatetimeoffset-confusion",{"title":296,"description":351},"articles\u002Fdatetimeoffset-confusion",[357],"netcore","zG8xVy_DOEaTRfDorK1eSmB3Hsgh4_eKm67fJnLbiak",1781574766041]