Manual package install in atom

I was having problems installing atom packages at work (on a Windows 7 machine) and I really wanted to have syntax highlighting in my React project.  Turns out it's really simple to manually install a package. 

Download the package you want. It's probably in GitHub.  I wanted the Atom React Package.

Extract the zip file and put it in the packages folder.  You can find this folder from the install packages screen:
 
Open a command window in the folder you just put in the packages directory. 

Run apm link 

Restart Atom and you're done.

Comments

  1. Unknown23 November 2017 at 02:28

    In any case, with standard drivers, things are much simpler, but otherwise, I would advise still resorting to Download Drivers for Windows http://bitdrivers.com/ only in a verified source. As usual, you may fix your system files for x64 or x32 bit)

    ReplyDelete
  2. Seo Hacker30 December 2017 at 01:33

    Thanks for a very interesting blog. What else may I get that kind of info written in such a perfect approach? I’ve a undertaking that I am simply now operating on, and I have been at the look out for such info. manual blog commenting

    ReplyDelete
  3. James jones11 September 2018 at 06:14

    This subtle process is specifically effective as soon as you possess a product or service that caters to some remarkably specialized niche of buyers. By crafting a highly focused message at a group of receptive shoppers, we are able to deliver a greatly synergized and effective buyer knowledge. AMREP’s in-process inspection

    ReplyDelete
  4. Abdul wasay14 September 2018 at 05:14

    I’m impressed, I must say. Really rarely do I encounter a blog that’s both educative and entertaining, and without a doubt, you might have hit the nail for the head. Your thought is outstanding; ab muscles an element that not enough people are speaking intelligently about. I will be happy that I found this inside my hunt for some thing with this. quality control in aerospace industry

    ReplyDelete

Post a Comment

Popular posts from this blog

Testing functions that use local storage with Jest

Testing functions that use the browsers local storage API seems easy when you know how. Here's a quick run down on how to mock it out with Jest if, like me, you're not familiar with how to test it. In the end it's very little code. Consider the following TypeScript code. import { get, save, key } from "./storage"; describe(save, () => { let setItem: jest.Mock; beforeEach(() => { setItem = jest.fn(); Storage.prototype.setItem = setItem; }); it("should call set item with predefined key and json object", () => { const valueToStore = { value: "toStore" }; save(valueToStore); expect(setItem).toHaveBeenCalledWith(key, JSON.stringify(valueToStore)); }); }); The key lines are in the beforeEach call where the setItem function of the Storage prototype is assigned to an instance of jest.fn() . This allows us to make assertions on what is passed to the local storage setItem API.
Read more

Solving `Empty reply from server` in DotNet Core

tldr; If you’re getting  curl: (52) Empty reply from server  check that you’ve configured Kestrel correctly. Long version I’ve started playing with Dotnet Core and Docker and have had a few issues getting started. I’ve had a little bit of experience with Docker, though only a little. I’ve worked with DotNet previously but never with Core. Environment The setup I’m using is a Windows laptop running Vagrant. Via Vagrant I’m running an Ubuntu Virtual Machine with the Docker run time installed. Feels a litle like inception. Key Problem The key problem that I’ve had getting started was having my Docker container not responding correctly to my curl commands. I get this: curl: (56) Recv failure: Connection reset by peer curl: (52) Empty reply from server Given that I’m not all that familliar with Docker or Dotnet Core I decided to remove one of the variables and set up a simple Express app in a different docker container. This validated that the commmand I was usin...
Read more

Can't resolve DNS Aws

Image
I recently registered a domain for a joke website  saladsimulator.com .  I figured I could whip up the page in a couple of minutes and throw it up on AWS using S3 static site hosting.  All done in an hour or so. What I thought would take an hour ended up in a multi-day ordeal while I tried to get the DNS to resolve.  I went through what seem to be the typical problems. The bucket wasn't configured to be accessible as a website. My bucket wasn't named the same as the website; the bucket needed to be saladsimulator.com to match the domain saladsimulator.com . I got these fixed up and found that it still wasn't working.  I added extra routes in to see if I could Alias or CNAME to a known working site, but they didn't work either. So it seemed it was a problem with something to do with the DNS configuration. After searching around I found a mention in a thread that the name server records in the hosted zone needed to match those in the domain name registrat...
Read more