Works great on Windows 10 can you make the website say that

From @davidpett on February 18, 2015 3:39

looking at the api, I would like to create an app to search themes and display them. The api endpoints are there, but I cannot consume them via ajax because of CORS.

Can you add a https://atom.io/crossdomain.xml to allow access?

Copied from original issue: atom/atom#5603

From @mnquintana on May 3, 2015 15:58

Those are all different pages on atom.io – no idea which is which. Pages on atom.io should have dynamic titles to reflect their content to avoid this kind of tab hell.

Copied from original issue: atom/atom#6624

From @ssorallen on August 6, 2015 22:45

This is a suggestion based on Ruby's documentation site (like http://ruby-doc.org/core-2.2.0/Array.html for example).

Currently each class documentation page for Atom (like https://atom.io/docs/api/v1.0.5/TextEditor for example) attempts to be both a table of contents and the content itself by collapsing all sections by default. This makes searching for content difficult with Cmd/Ctrl + f. If the table of contents, the list of properties and methods, instead lived in the left bar then the main content area would not need to behave like a table of contents as well and could avoid collapsing content at all.

Copied from original issue: atom/apm#414

I haven't tested other IE versions, but if I download Atom (from https://atom.io/download/windows ) using IE11, the downloaded file is called "AtomSetup" (with no extension), and can't be double-clicked.

If I use Firefox on the same computer, I get "AtomSetup.exe", and all works OK.

The "writing specs" page should at the very least, link to the spec-helper file in atom so that package/PR authors can see what helpers are available when writing specs.

So far, it looks like the list is

• jasmine-jquery - already well documented, a link is good enough.
• toBeInstanceOf
• toHaveLength
• toExistOnDisk
• toHaveFocus
• toShow - Tests if the element is visible in the dom.

Originally discussed on slack, when I was trying to find this information.

edit: I'll be submitting a PR on docs

Can you add the source code so we can easily contribute?

Since a picture says more than a thousand words, or some such...

We should reference the OS/platform as OS X, not OSX or Mac. Mac is the hardware platform that runs the OS, not the OS itself. And OSX is simply a misspelling of the name.

Hi there

I raised an issue on the atom discussion boards about the lack of an RSS feed for package releases and updates. Somebody kindly pointed out that there is one, but they had to search for it to find it.

Maybe a link to it could be added to the "Keep in Touch" section at the bottom of the page?

Now I've found the RSS feed, my original issue isn't quite so important - I was wondering about displaying dates/times on the packages page. It might still be quite useful though.

Cheers,
Nige

From @boustanihani on February 17, 2015 11:4

Could you please allow sorting search results on https://atom.io/packages & https://atom.io/themes by the number of downloads and the number of stars ?

And maybe also inside the Atom Editor...

Copied from original issue: atom/apm#303

The 2nd to last grid item for "Recently Updated" doesn't line up correctly for some reason.

From @blaisck on June 30, 2015 2:7

Installing “[email protected]” failed.Hide output…
Unable to download https://www.atom.io/api/packages/powerline/versions/0.1.0/tarball: 400 Bad Request Repository inaccessible

Copied from original issue: atom/atom#7567

From @jonasws on July 5, 2015 22:8

I have been trying for a while to publish my package github-utils, but I keep getting the following error when I try to run apm publish minor

Registering package in jonasws/github-utils repository failed: 
That repo does not exist, isn't an atom package, or you do not have access

I do indeed have access to the repo. I have tried to do apm login. Is something at fault with my Atom.io account user? Any comments would be greatly appreciated!

Copied from original issue: atom/apm#393

If it was, I'd just send a PR for things like #29 😉

From @ssorallen on August 11, 2015 0:36

This is related to atom/atom#8124

Lowercase JavaScript primitives should link to https://developer.mozilla.org/en-US/docs/Glossary/Primitive.

Atom's documentation mostly refers to the uppercase wrapper objects like Boolean, Number, and String, but nearly all of those uses should reference the lowercase primitives boolean, number, and string instead. atom.io links {Boolean}, etc. to the wrapper objects, but it's unclear if it correctly links primitives like {boolean} to a doc describing primitives like https://developer.mozilla.org/en-US/docs/Glossary/Primitive.

Copied from original issue: atom/apm#415

The atom/atom repository and Discuss point to v1.3.0.

From @mark-hahn on January 22, 2015 20:54

I would like to see an "about us" page on atom.io. It should have a photo and short bio for every core team member along with primary responsibilities. Many consider these public relations junk but I for one would like to see faces on the people that have such a big impact on Atom. I think this would put a human face on the project and make it more welcoming.

Also a brief history of Atom, motivation for creating Atom, and a vision for the future would be nice.

Normally on an open-source project it would be hard to pick out contributors to be considered "core" but here it would be any github employee assigned to Atom.

Copied from original issue: atom/atom#5223

It's an annoying and confusing experience to only encounter a changelog on some apps and see it missing on others, I would love to see having this as a requirement to being able to host packages on atom.io.

There are README.md files of packages like this one that point to parts of the same page that work just fine in github but not in atom.io because the target of those anchors don't have the expected id attribute.

for example:

works: https://github.com/suda/tool-bar#plugins
doesn't work: https://atom.io/packages/tool-bar#plugins

what was expected: expected to go to the plugins section
what happened: end it up in the top of the page

We are receiving reports of numerous people referring to old documentation because when they click "go to latest" from really old links, it takes them to v0.186.0, i.e. pre-atom/docs documentation. It would be better if things like https://atom.io/docs/v0.186.0/your-first-package was redirected to https://atom.io/docs/latest and have to find the "your first package" stuff than to be stuck looking at outdated and ever-increasingly incorrect documentation.

Hi,
I've been trying to setup semantic-release workflow for my plugin today with last-release-apm adapter and I didn't got the configuration right on the first time and now my package seems pretty badly messed up : see here https://atom.io/api/packages/fast-eslint

Could you clean the DB a bit from v1.1.3 please ?
Thx !

If "undefined" appears in a docblock, the word does not make it to the generated documentation. One example is for PackageManager::getLoadedPackage.

Source:

Generated doc:

It appears that the releases are listed in date order, when it would probably be best if they were in semver order (see item number 11 of the specification).

According to semver, they should be (from top to bottom):

• v1.1.0
• v1.1.0-beta1
• v1.0.19

Any search query to https://atom.io/packages/search?q= is currently generating a 500 error. I'm not sure what is the problem.

From @Sheng-Bo on July 7, 2015 15:16

This is the package I want to remove from Atom package repository:
https://atom.io/packages/chinese-menu

Would you please remove it for me manually? Because I am afraid that this broken package could cause confusion for Atom users.

My suggestions:

1. Is it possible to have a "delete package" button on my Atom user profile page?
2. Is it possible to use APM to log into GitHub before unpublish my package?

Thanks so much.

Reference: https://discuss.atom.io/t/cannot-unpublish-package-once-github-repository-deleted/18580

Copied from original issue: atom/apm#394

From @noseglid on May 12, 2015 19:34

Not sure if this is where this issue should go. Please direct me to the correct forum otherwise.

I get this:

$ apm publish -t v0.32.0
Publishing [email protected] ✗
Creating new version failed: Application error

I've debugged a little, and it appears I get 500 Internal Server Error from the API. So likely something is off with whatever apm communicates with.

Copied from original issue: atom/apm#364

We should have a separate "Experimental" section or they should at least only show up in "Extended".

in the PackageManager#enablePackage() documentation, there's a broken link to Package.

From @ssorallen on August 6, 2015 22:37

Surfacing type information in method signatures would make scanning the docs more valuable. For example from the TextEditor (https://atom.io/docs/api/v1.0.5/TextBuffer#section-Mutating%20Text):

Currently:

::setTextInRange(range, text, [options])

::insert(position, text, [options])

Surfacing type information in the signature:

::setTextInRange(range: Range, text: string, options?: Object): Range

::insert(position: Point, text: string, options?: Object): Range

The examples are formatted to fit Flow's type annotations.

Copied from original issue: atom/apm#413

From @russlescai on May 31, 2015 22:30

I know this is minor in the scheme of things, but I noticed the homepage for https://atom.io still has the Atom Dark theme, not the One Dark UI theme as the screenshot.

Copied from original issue: atom/atom#7043

From @mnquintana on January 26, 2015 23:39

It would be really helpful to show the release date for the latest version of a package on atom.io (or if not a date, time since the last release). This would make it a little easier to weed out packages that might not be maintained anymore. Maybe something like:

Copied from original issue: atom/apm#277

In this page the link to the Atom API in the first paragraph of the content leads to this link. The correct link would be this.

• Correct link : https://atom.io/docs/api/v1.3.2/AtomEnvironment
• The mistake : https://atom.io/docs/api/v1.3.2/Atom

I cannot follow the atom blog (with ifttt) because it is no valid xml:

https://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fblog.atom.io%2Ffeed.xml

From @mnquintana on January 21, 2015 15:16

Now that Atom is available for all platforms, I think it would be better UX to instead actually show the releases for the other platforms when you click "Other platforms" from the home page. Right now, it just redirects to the FAQ question, which just states that builds are available for all of these platforms, but doesn't actually direct you to download them (instead it seems to suggest that you have to compile it yourself if you want to use it).

Copied from original issue: atom/apm#266

Currently, https://atom.io/releases shows the full list of changes (e.g. all merged PRs) for each minor release, including the Notable Changes, which can be quite overwhelming. Here's what I'm thinking:

1. Only show Notable Changes in the index view at https://atom.io/releases
2. Add a new view for showing a single release (e.g. https://atom.io/releases/v1.3.0). This view would show the full list of changes (e.g. all merged PRs) for that release.
3. Change GitHub release links in index view to point to the new view at https://atom.io/releases/[version]
4. Add a link to view the release on GitHub to the new view at https://atom.io/releases/[version]

This way, https://atom.io/releases would be a summary of notable changes, and users would click on a particular release to get more detail about the changes.

What do you think?

Was browsing around and noticed that the following link was 404ing. Looks like the address was changed however the link was never updated.

The link is from Flight Manual -> 2: Using Atom -> Atom Packages (highlighted below)

From @jacekkopecky on August 6, 2015 20:44

The listing sorted by stars seems to be incomplete: https://atom.io/packages/list?direction=desc&sort=downloads shows vim-mode there with many downloads and 505 stars, but https://atom.io/packages/list?direction=desc&sort=stars doesn't show vim-mode even though its 505 stars should put it right after highlight-selected.

Copied from original issue: atom/apm#412

From @sumyungguy on December 3, 2015 15:37

I'm a new user having trouble with some broken community packages. I was looking for general information on how packages are published to atom.io, who is responsible for them, and how I could perhaps contribute to fixing them, particularly when the original author is no longer active or responding to pull requests and so on. Eventually I tracked down the info, but I found it difficult to locate.

In the FAQ at https://atom.io/faq the two links under "How can I contribute to Atom?" are broken:

1 - "creating a package" - https://atom.io/docs/latest/creating-a-package
The content formerly at this URL has been mostly merged into "package: word count":
https://atom.io/docs/latest/hacking-atom-package-word-count
...and that seems to be the most appropriate place for the FAQ link to go to.

The "package: word count" title is somewhat unintuitive compared to the former "creating a package", and despite spending some time looking through the site, I only found the info about publishing by putting the broken link from the FAQ into the Wayback Machine at archive.org. There's not much to indicate that this single page contains the majority of the reference info about writing, debugging, and publishing packages.

I see in the planning outline that there's a whole chapter on contributing being considered, but in the meantime a little cleanup might be helpful. I'd like to suggest having a more descriptive name for the "package: word count" page, a better explanation of the contents in the opening paragraph, and maybe either a mini table of contents at the top of the page, or breaking out some of the sections separately so they can appear in the main table of contents, eg. creating, testing and debugging, and publishing. You might also consider renaming section 3.7 from "debugging" to "troubleshooting", since actual debugging is covered in the packages page.

The info about publishing could perhaps be moved or at least linked to the "Maintaining Your Packages" section in chapter 4, which is the first place I looked, but only found info on unpublishing...

2 - "contributing guide" - https://atom.io/docs/latest/contributing
This content is in the atom master at https://github.com/atom/atom/blob/master/CONTRIBUTING.md and contains all kinds of very useful information... but I couldn't find it anywhere in the docs site, and again only located it by putting the broken FAQ link into the Wayback Machine.

Copied from original issue: atom/flight-manual.atom.io#146

From @mnquintana on August 5, 2015 22:17

Challenge

Being a very modular project, Atom has a lot of changes happening across a lot of repos. This can make it quite a challenge to keep track of all the changes being made in Atom from version to version. Unfortunately, that has sort of meant that our release notes end up being rather bare-bones summaries of what's changed in any particular version, rather than complete, well, changelogs. In addition, none of our bundled packages or libraries have any release notes at all right now - it's only Atom core.

I think it's important to publicly document every significant change we make to Atom across all of our repos, which should make it a lot easier for users to know what to expect from each release, and hopefully help prevent surprises like atom/toggle-quotes@8899f00#commitcomment-12552713 or atom/atom#8226.

Proposal

1. Add CHANGELOG.md files to each package and library repo (or leverage GitHub Releases)
   • I'm personally 👍 for CHANGELOG.md files - they're version-controlled, simple to update, easy to discover, and will be displayed properly in settings-view.
2. Add a CHANGELOG.md to atom/atom to be used exclusively for core changes
3. Update them individually with each significant changes as they are made
4. Concatenate and organize all changelogs for atom.io/releases
   • For UI here it might be nice to take some inspiration from Firefox release notes - default to the short summary display, and offer a "view full list of changes" option for those who really want to dig deeper.
   • Maybe even add the ability to filter by package / library?
5. atom/atom release notes (ie. the notes used in GitHub Releases, rather than the CHANGELOG.md) can continue to work as the short summary of what changed.

/cc @atom/feedback

Copied from original issue: atom/atom#8240

Creating new version failed: Application error
I can't publish my package~
This bug again? I hope I can fix it

Had to start the build process three times before it made it all the way through this morning:

[master][~/Source/atom] script/build
Node: v1.8.1
npm: v2.13.3
Installing build modules...
Installing apm...
Installing modules ✓
Installing [email protected] ✗
Unable to download https://www.atom.io/api/packages/atom-dark-ui/versions/0.50.0/tarball: 503
[master][~/Source/atom][1] script/build
Node: v1.8.1
npm: v2.13.3
Installing build modules...
Installing apm...
Installing modules ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✗
Request for package information failed: atom.io is temporarily unavailable, please try again later.
[master][~/Source/atom][1] script/build
Node: v1.8.1
npm: v2.13.3
Installing build modules...
Installing apm...
Installing modules ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✓
Installing [email protected] ✓
Deduping modules ✓
Running "download-atom-shell" task

Running "download-atom-shell-chromedriver" task

Running "build" task

Running "coffee:glob_to_multiple" (coffee) task

I feel like the services provided or consumed by the Atom default-installed packages (autocomplete-plus, status-bar, tree-view, tabs, etc) should be documented in a central location rather than only in the package README. This would make the most sense in the developer documentation, but there isn't a way to include this currently implemented.

Please add a capability to document Atom provided or consumed services in the developer documentation.

Just using an old version of ZeroClipboard, right?

I'm having no success in trying to publish my package.

apm login works, but every apm publish minor keeps returning:

I got prompted for my Github credentials once, which I provided an access token for (I'm using 2FA), but it never seems to work.

Running git from my command line works fine when managing my other github repos.

I'm happy to completely wipe my atom account clean and try again.

Entire details of the problem are described in the atom discussion forum:
https://discuss.atom.io/t/publishing-packages-doesnt-prompt-for-github-credentials-fails/19490

From @tinloaf on April 20, 2015 17:16

Hi,

visiting https://atom.io/docs/v0.60.0/publish-a-package gives me a 500 error message and tells me to let you know if a refresh does not solve the problem. Well, it does not. ;)

Copied from original issue: atom/atom#6444

From @peterhal on July 9, 2015 18:1

Github supports relative URLs for things like images in markdown files. The Atom generated package docs do not.

For example compare these:

https://atom.io/packages/nuclide-flow

And:

https://github.com/facebook/nuclide/tree/master/pkg/nuclide/flow

The relative image URLs work in the github page, but not the Atom page.

Copied from original issue: atom/atom#7819

Also causing atom/atom#3801

This is a problem that plagues all the normal release channel of Github projects, including Atom.

I do not intend to bring political debate, but for now this is a rather big obstacle between Chinese developers and Atom which other editors such as Sublime Text and Notepad++ doesn't suffer from.

From @MohamedTita on October 27, 2015 0:23

Unable to download https://www.atom.io/api/packages/color-picker/versions/2.0.13/tarball: DEPTH_ZERO_SELF_SIGNED_CERT

O.S Fedora 22

Copied from original issue: atom/atom#9298

From @mnquintana on January 20, 2015 19:40

It would be really useful to see what version number you'll be downloading when you hit one of the download buttons on atom.io. Of course, you could always check Atom's releases on GitHub and download from there, but it would be nice to see the version number on the website too, preferably by the download buttons.

Copied from original issue: atom/apm#263

Trying to install a package, getting this error:

Request for package information failed: atom.io is temporarily unavailable, please try again later.