# Kibana 4.4.1 - unable to npm start or build **URL:** \ **Category:** Kibana\ **Created:** [February 29, 2016, 7:06pm UTC](https://discuss.elastic.co/t/kibana-4-4-1-unable-to-npm-start-or-build/43035 "2016-02-29T19:06:31Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jliang](https://avatars.discourse-cdn.com/v4/letter/j/e8c25b/32.png) [@jliang](https://discuss.elastic.co/u/jliang)\ **Post date:** [February 29, 2016, 7:06pm UTC](https://discuss.elastic.co/t/kibana-4-4-1-unable-to-npm-start-or-build/43035/1 "2016-02-29T19:06:31Z")
I just download the Kibana 4.4.1 and tring to make some changes which I juse to do for kibana 4.3 or previous versions. But nothing was apply when I use bin/kibana. And npm start is no longer working. And also how can I build? Like to create the packages? ---
**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\ **Post date:** [March 1, 2016, 12:43am UTC](https://discuss.elastic.co/t/kibana-4-4-1-unable-to-npm-start-or-build/43035/2 "2016-03-01T00:43:07Z")
You could clone the repo at [https://github.com/elastic/kibana](https://github.com/elastic/kibana), checkout v4.4.1, apply your changes and then run `npm run build` to build a distributable. This is how we build the binaries that are downloadable on the site. What type of changes are you making specifically though? Most changes should still get picked up in 4.4.1, as far as I know. ---
**Author:** ![jliang](https://avatars.discourse-cdn.com/v4/letter/j/e8c25b/32.png) [@jliang](https://discuss.elastic.co/u/jliang)\ **Post date:** [March 1, 2016, 10:14pm UTC](https://discuss.elastic.co/t/kibana-4-4-1-unable-to-npm-start-or-build/43035/3 "2016-03-01T22:14:37Z")
Hi Matt, Thanks for your reply. We are adding some changes like maturity ticks. And I found when I try to run bin/kibana, only if I made some changes for installed Plugins like marvel or something, it will be force to optimize again and will take all changes in kibana. Otherwise only run bin/kibana will not take any changes. Is it new in v4.4.1? Thanks very much and it helps. ---
**Author:** ![stormpython](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stormpython/32/7190_2.png) [@stormpython](https://discuss.elastic.co/u/stormpython)\ **Post date:** [March 1, 2016, 11:34pm UTC](https://discuss.elastic.co/t/kibana-4-4-1-unable-to-npm-start-or-build/43035/4 "2016-03-01T23:34:26Z")
You may have to remove your `node_modules` directory, ```auto rm -rf node_modules ``` and ```auto npm install ``` to get the `npm start` command to continue working. You may also want to remove your `bundles` directory: ```auto rm -rf optimize/bundles ``` to get a fresh bundle, but this should only need to happen once after you get `npm start` working again. ---
**Author:** ![Bargs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bargs/32/5429_2.png) [@Bargs](https://discuss.elastic.co/u/Bargs)\ **Post date:** [March 2, 2016, 1:15am UTC](https://discuss.elastic.co/t/kibana-4-4-1-unable-to-npm-start-or-build/43035/5 "2016-03-02T01:15:42Z")
And if you're only trying to make frontend changes, I would try deleting `optimize/bundles` and restarting the server before going down the route of deleting node\_modules. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:00pm UTC](https://discuss.elastic.co/t/kibana-4-4-1-unable-to-npm-start-or-build/43035/6 "2017-07-06T14:00:38Z")