Go to file
Dimitri Mitropoulos a060562697
Fixes clean scripts (#3400)
* removes (unused and unwanted) husky scripts

might as well, it's only taking up space for nothing in our node_modules

* adds `lerna run clean` to main clean script

we didn't have `clean` scripts in the packages before, but now that we do, it makes sense to.... hahah... _use them_.

Note that it's important that we run the package scripts first, because otherwise after the rimraf (which is now at the end) there's no `lerna` left to call.

* adds missing clean script to insomnia-components

although it looks like there are other changes at first glance, there shouldn't be any behavioral differences now except the fact that build will always generate SVGs (which, was an oversight/bug that it wasn't before).  We need this to occur so that when we clean it removes the things that were built, and when we build it replaces those same things.

* adds a postclean script to insomnia-app like every other package

I'll be honest, I'm not entirely sure what the reason is for having `postclean` scripts in every package with (mostly) `rimraf dist` (i.e. instead of just including that in the main clean script at the end), but that's clearly the convention - so for now I'm just following it

* removes references to old build artifact location

well, except for the .gitignore.  I guess I could remove it from the .gitignore, commit it, commit deleting it, which would clear it from everyone's projects... but I'll just leave it there for a bit in the .gitignore.  hopefully people either start fresh or run `clean` from the root every once in a while, which will clean this up.

After a few weeks or months we can remove these two references (in the package.json.clean and .gitignore) altogether if we feel like it.

* removes unused reference in config to build artifact

I searched high and low for every place I could find that consumes this file and none of them seem to use this field anyway.  And even if they did, it's wrong.  In fact, it's been wrong for a while I'd guess because (relative to the root, if that's what it was intended to mean).

As far as I can tell this was added c6a7c4d682 (diff-6918d2464ad7fb0f3e985d8587ce0c4218eeba6c6dea60c58642251f4db99ecb)

So I even checked out that commit and looked at all usages of that file at that time and it was, there too, unused (so far as I can tell).  Appears to be a case of wishful thinking that it'd be useful for something, not sure.
2021-05-19 09:56:10 -04:00
.github Publish NPM packages through CI (#3311) 2021-05-15 09:09:11 +12:00
packages Fixes clean scripts (#3400) 2021-05-19 09:56:10 -04:00
plugins chore: add repository, bug urls, and license to plugins missing it (#3379) 2021-05-13 07:31:33 -04:00
screenshots chore: add new screenshot for readme (#2059) 2020-04-28 13:57:06 -07:00
scripts [TypeScript] Phase 1 & 2 (#3370) 2021-05-12 18:35:00 +12:00
.dockerignore
.editorconfig [TypeScript] Phase 1 & 2 (#3370) 2021-05-12 18:35:00 +12:00
.eslintignore [TypeScript] Phase 1 & 2 (#3370) 2021-05-12 18:35:00 +12:00
.eslintrc.js [TypeScript] Phase 1 & 2 (#3370) 2021-05-12 18:35:00 +12:00
.gitattributes
.gitignore [TypeScript] Phase 1 & 2 (#3370) 2021-05-12 18:35:00 +12:00
.nvmrc Fix webpack file watching, remove styled-components from insomnia-components bundle (#2497) 2020-08-11 07:12:53 +12:00
CODE_OF_CONDUCT.md Update CODE_OF_CONDUCT.md (#2343) 2020-07-14 11:32:54 +12:00
CONTRIBUTING.md Add Contributor Shirt Details (#2135) 2020-05-08 12:20:27 +12:00
DEVELOPMENT.md Improve documentation (#2990) 2021-01-12 15:23:20 +13:00
jest-preset.js remove duplication of all jest configs (#3375) 2021-05-13 07:29:02 -04:00
lerna.json Update lerna version message (#3393) 2021-05-19 11:27:09 +12:00
LICENSE Remove copyright year in MIT license 2019-05-20 11:24:55 -04:00
package-lock.json Fixes clean scripts (#3400) 2021-05-19 09:56:10 -04:00
package.json Fixes clean scripts (#3400) 2021-05-19 09:56:10 -04:00
README.md chore: remove codefund badge, update license badge (#3229) 2021-03-26 09:23:32 -07:00
tsconfig.base.json [TypeScript] Phase 1 & 2 (#3370) 2021-05-12 18:35:00 +12:00
tsconfig.eslint.json remove duplication of all jest configs (#3375) 2021-05-13 07:29:02 -04:00

Insomnia REST Client

Slack Channel license

Insomnia is a cross-platform REST client, built on top of Electron.

Insomnia REST Client Screenshot

Download

Insomnia is available for Mac, Windows, and Linux and can be downloaded from the website.

https://insomnia.rest/download

Bugs and Feature Requests

Have a bug or a feature request? First, read the issue guidelines and search for existing and closed issues. If your problem or idea is not addressed yet, please open a new issue.

For more generic product questions and feedback, join the Slack Team or email support@insomnia.rest

Contributing

Please read through our contributing guidelines and code of conduct. Included are directions for opening issues, coding standards, and notes on development.

Editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at editorconfig.org.

Developing

Development on Insomnia can be done on Mac, Windows, or Linux as long as you have NodeJS and Git. See the .nvmrc file located in the project for the correct Node version.

Initial Dev Setup

This repository is structured as a monorepo and contains many Node.JS packages. Each package has its own set of commands, but the most common commands are available from the root package.json and can be accessed using the npm run ... command. Here are the only three commands you should need to start developing on the app.

# Install and Link Dependencies
npm run bootstrap

# Run Tests
npm test

# Start App with Live Reload
npm run app-start

If you are on Linux, you may need to install the following supporting packages

# Update library
sudo apt-get update

# Install font configuration library & support
sudo apt-get install libfontconfig-dev
sudo apt-get install font-manager

# Build capability for required font-scanner package
sudo apt-get install build-essential

Also on Linux, if Electron is failing during the bootstrap process, run the following

# Clear Electron install conflicts
rm -rf ~/.cache/electron

If you are on Windows and have problems, you may need to install Windows Build Tools

Editor Requirements

You can use any editor you'd like, but make sure to have support/plugins for the following tools:

  • ESLint For catching syntax problems and common errors
  • JSX Syntax For React components
  • Flow For type annotations

Plugins

Search, discover, and install plugins from the Insomnia Plugin Hub!

Community Projects

License

MIT © Insomnia