Reduce Prism.js bundle size by stripping unused languages and plugins - #865

Thanks @Amrit-raj50 !

@sivaraam, since you were involved in the previous syntax highlighting improvements, can you take a look at this too?

@chriscool , @sivaraam could you review this , so that i can apply changes if any .

Why is the prism.css unchaged? Would it not change too?

Regarding the non-language content in your comment:

non-language contents --> Git Commit Graph/Log/Patch Header,Plain Text / Terminal Output / Benchmark

I think we can use the command-line plugin for terminal output.

Some helpful doc about this in README would be useful.

thanks @sivaraam , i will check the README

hi @sivaraam ,
I have reserched for the commandline styling and i get to know that
we can apply it in two different ways at first i will tell you the difference between them

1. command line plugin :
   files need to add ---> prism-command-line.js + .css
   real senario:
   when a writer when writing in any .md file and he/she needs to want add commands in the file in the "command line plugin" senario
   he/she have to always repeat that which line is a output and which is a command with the help of a commnd below the real commands in the file
   i.e; {: .command-line data-output="..."}

but when he/she needs to update the commands in the file again he/she has to update the ; {: .command-line data-output="..."} , otherwise it rendered wrong way ....so this is constraint for using command line plugin.

2. prim's console grammar :
   files need to add ---> prism-command-line.js
   same senario but here he/she do not have to count the line after any updation he/she just need to put $ any line without $ considered as output and with $ considered as input.

so , now tell me sir which one should i apply
and also i have to mention these changes in the CONTRIBUTING.md , for the writers to understand how to write commands in the files

thankyou

Why is the prism.css unchaged? Would it not change too?

there is no need to change the .css file it is already up-to-date

so , now tell me sir which one should i apply

I think second one makes more sense. We can go with it. Could you add some guidelines alone in the README?

and also i have to mention these changes in the CONTRIBUTING.md , for the writers to understand how to write commands in the files

This does not really fit the CONTRIBUTING.md which should ideally be about guidelines related to contributing process

there is no need to change the .css file it is already up-to-date

Could you add the header comment there too?

Also check Christian's comment here.